← previous blocknext block →recent activity
Analyzing
Block #71,066,092
6 transactions · 6 stateful · 2026-04-28 10:52:49 UTC
Parallelism
50/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,066,092 · 6 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x1d5e76c7…d17e
0x065c9d…c394
4 touches
1 conflict
0x231af64a…821c
0x065c9d…c394
4 touches
1 conflict
0xe59a8bf9…e624
0x065c9d…c394
4 touches
1 conflict
0xf3c205b2…9b5a
0x065c9d…c394
4 touches
1 conflict
0xe52790c8…722e
0x065c9d…c394
2 touches
1 conflict
0xfb4491ac…a922
0x065c9d…c394
2 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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity