← previous blocknext block →recent activity
Analyzing
Block #72,271,324
7 transactions · 6 stateful · 2026-05-04 00:48:30 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,271,324 · 7 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17e2d2a0…359e
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a8
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ab
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
3 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
3 touches
1 conflict
0x03924cd3…f268
0x8d66a4…3095
3 touches
1 conflict
0x143dba04…1b98
0x8d66a4…3095
3 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
1 conflict on slot 0x17e2d2a069…81359e
Audit this contract →
← previous block·next block →recent activity