← previous blocknext block →recent activity
Analyzing
Block #71,330,311
27 transactions · 23 stateful · 2026-04-29 16:12:05 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #71,330,311 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w111w012w113w214w015w116w217w320w321w422w323w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x6c395e14…0158
0xd32edf…ff58
7 touches
6 conflicts
0x0eac6378…36f4
0x34b655…2a6f
6 touches
3 conflicts
0x150af51d…9c42
0x34b655…2a6f
6 touches
3 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
6 touches
3 conflicts
0x2877f440…c2c8
0x34b655…2a6f
6 touches
3 conflicts
0x3254d19b…f714
0x34b655…2a6f
6 touches
3 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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity