← previous blocknext block →recent activity
Analyzing
Block #71,283,791
20 transactions · 17 stateful · 2026-04-29 11:02:07 UTC
Parallelism
90/100
Blocked
24%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,283,791 · 20 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
2w03w18w09w110w011w116w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0520da1d…c88e
0x34b655…2a6f
4 touches
1 conflict
0x052887af…89a3
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x150af51d…9c42
0x34b655…2a6f
4 touches
1 conflict
0x3254d19b…f714
0x34b655…2a6f
4 touches
1 conflict
0x3e0f56fb…e78f
0x34b655…2a6f
4 touches
1 conflict
0x414e9446…4b59
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
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
1 conflict on slot 0x0520da1d71…06c88e
Audit this contract →
← previous block·next block →recent activity