← previous blocknext block →recent activity
Analyzing
Block #74,518,246
11 transactions · 10 stateful · 2026-05-14 10:27:03 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,518,246 · 11 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
1w05w16w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x88ab4d92…bc2f
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0xcf42b35b…b855
0x065c9d…c394
3 touches
1 conflict
0xf6638309…84ed
0x065c9d…c394
3 touches
1 conflict
0x2002cf49…f8a6
0x065c9d…c394
3 touches
1 conflict
0x5a0a316d…ba8d
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
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: Perpl
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity