← previous blocknext block →recent activity
Analyzing
Block #71,045,210
14 transactions · 11 stateful · 2026-04-28 08:33:48 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,045,210 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3981be5…2c47
0x34b655…2a6f
8 touches
6 conflicts
0x031d16b4…895a
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x0d3d3160…bb17
0x34b655…2a6f
4 touches
1 conflict
0x2734e46d…e50d
0x34b655…2a6f
4 touches
1 conflict
0x3254d19b…f714
0x34b655…2a6f
4 touches
1 conflict
0x3c35979a…975d
0x34b655…2a6f
4 touches
1 conflict
0x414e9446…4b59
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
6 conflicts on slot 0xf3981be56e…f02c47
Audit this contract →
← previous block·next block →recent activity