← previous blocknext block →recent activity
Analyzing
Block #72,221,806
8 transactions · 8 stateful · 2026-05-03 19:15:47 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,221,806 · 8 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x220f4f84…15f8
0x34b655…2a6f
6 touches
3 conflicts
0xc53af6f0…50bd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x6eab912e…935d
0x065c9d…c394
2 touches
0 conflicts
0xcde8399c…d07a
0x065c9d…c394
2 touches
0 conflicts
0xf9c48ead…df92
0x065c9d…c394
2 touches
0 conflicts
0xffaa4bff…c026
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 0x220f4f84fa…a015f8
Audit this contract →
← previous block·next block →recent activity