← previous blocknext block →recent activity
Analyzing
Block #72,981,411
12 transactions · 11 stateful · 2026-05-07 07:40:53 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,981,411 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb389d45f…8a4c
0x34b655…2a6f
6 touches
3 conflicts
0x92339d95…0800
0x0000a8…8888
4 touches
1 conflict
0x25f8183e…b2d2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4f91fd62…d68e
0x065c9d…c394
2 touches
0 conflicts
0x80d29a80…8ad9
0x065c9d…c394
2 touches
0 conflicts
0x8a9daa67…d0ab
0x065c9d…c394
2 touches
0 conflicts
0xbd7e37a9…9eb5
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
3 conflicts on slot 0xb389d45f2b…a98a4c
Audit this contract →
← previous block·next block →recent activity