← previous blocknext block →recent activity
Analyzing
Block #71,037,858
8 transactions · 7 stateful · 2026-04-28 07:44:51 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,037,858 · 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
3w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b47c88e…e0ff
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb42d65f9…743c
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
6 touches
3 conflicts
0xdeb7ae83…b45a
0x065c9d…c394
3 touches
1 conflict
0x8b2d35ff…7c15
0x065c9d…c394
3 touches
1 conflict
0x4d342079…7730
0x065c9d…c394
3 touches
1 conflict
0x17f25070…046a
0x065c9d…c394
3 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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x6b47c88e7d…f0e0ff
Audit this contract →
← previous block·next block →recent activity