← previous blocknext block →recent activity
Analyzing
Block #73,036,617
21 transactions · 14 stateful · 2026-05-07 13:48:14 UTC
Parallelism
90/100
Blocked
29%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,036,617 · 21 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
1w02w03w19w118w019w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b6d2deb…dde0
0x34b655…2a6f
4 touches
1 conflict
0x7f38bfbc…61e3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x32ee90db…decc
0x34b655…2a6f
2 touches
0 conflicts
0x388e001a…7e04
0x34b655…2a6f
2 touches
0 conflicts
0x4a03ceb5…a07f
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: Perpl
1 conflict on slot 0x7b6d2debd6…b6dde0
Audit this contract →
← previous block·next block →recent activity