Block #73,648,253

← previous blocknext block →recent activity

Analyzing

Block #73,648,253

13 transactions · 11 stateful · 2026-05-10 09:39:25 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,648,253  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0x2189fe5f…d43e

0x34b655…2a6f

2 touches
0 conflicts

0x2eab2661…2b15

0x34b655…2a6f

2 touches
0 conflicts

0x8a2657f5…e008

0x34b655…2a6f

2 touches
0 conflicts

0x999cad42…a8b2

0x34b655…2a6f

2 touches
0 conflicts

0xa6c2446c…b128

0x34b655…2a6f

2 touches
0 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x2a68ba18…8e90c5

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity