← previous blocknext block →recent activity
Analyzing
Block #71,643,590
9 transactions · 6 stateful · 2026-05-01 03:02:51 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,643,590 · 9 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x47f4b366…b115
0x065c9d…c394
4 touches
1 conflict
0x8dae8728…0de3
0x065c9d…c394
3 touches
1 conflict
0xa7b1913c…6942
0x065c9d…c394
3 touches
1 conflict
0xc1b8e3f3…062e
0x065c9d…c394
2 touches
0 conflicts
0xcbadeb73…0455
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity