← previous blocknext block →recent activity
Analyzing
Block #71,064,980
8 transactions · 7 stateful · 2026-04-28 10:45:24 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,064,980 · 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
1w02w14w05w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x03bf3018…12dd
0x065c9d…c394
2 touches
0 conflicts
0x1972573f…0033
0x065c9d…c394
2 touches
0 conflicts
0x26cfd365…a068
0x065c9d…c394
2 touches
0 conflicts
0x3cf150fe…4727
0x065c9d…c394
2 touches
0 conflicts
0x5415b8f2…298c
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity