← previous blocknext block →recent activity
Analyzing
Block #73,513,299
18 transactions · 16 stateful · 2026-05-09 18:39:56 UTC
Parallelism
61/100
Blocked
38%
Avg conflicts / tx
0.78
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,513,299 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x110a3804…f842
0x34b655…2a6f
6 touches
3 conflicts
0xce7c598a…631b
0x34b655…2a6f
6 touches
3 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x374426df…f445
0xc8689a…ee79
4 touches
1 conflict
0x2905340c…dbc6
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity