← previous blocknext block →recent activity
Analyzing
Block #71,696,408
8 transactions · 7 stateful · 2026-05-01 08:54:29 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,696,408 · 8 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
3w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa1a59ab4…eca9
0x065c9d…c394
4 touches
1 conflict
0x9c5ab33c…93b9
0x065c9d…c394
3 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x68851a97…aacb
0x065c9d…c394
2 touches
0 conflicts
0x6c3d188e…8fce
0x065c9d…c394
2 touches
0 conflicts
0x96b486ee…7736
0x065c9d…c394
2 touches
0 conflicts
0x9c20b920…9eeb
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity