← previous blocknext block →recent activity
Analyzing
Block #74,334,456
19 transactions · 12 stateful · 2026-05-13 14:02:32 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
0.84
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,334,456 · 19 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
2w04w19w010w114w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
8 touches
6 conflicts
0x97d5efed…1aa4
0x34b655…2a6f
6 touches
3 conflicts
0x4f483049…3cc7
0x34b655…2a6f
6 touches
3 conflicts
0xc106aa43…2443
0x34b655…2a6f
6 touches
3 conflicts
0x9be2b99a…a959
0x34b655…2a6f
4 touches
1 conflict
0xd6aabe89…92f5
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
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