← previous blocknext block →recent activity
Analyzing
Block #71,343,027
6 transactions · 5 stateful · 2026-04-29 17:36:55 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,343,027 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74262e8b…b1f8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4f0a1d12…49ee
0x065c9d…c394
3 touches
1 conflict
0x01d531ea…d025
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x4ec93cff…9db9
0x065c9d…c394
2 touches
0 conflicts
0xc73c097e…8c01
0x065c9d…c394
2 touches
0 conflicts
0xf701989b…0316
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
1 conflict on slot 0x74262e8be7…31b1f8
Audit this contract →
← previous block·next block →recent activity