← previous blocknext block →recent activity
Analyzing
Block #71,037,932
11 transactions · 9 stateful · 2026-04-28 07:45:21 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,037,932 · 11 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fd4b7e7…04ee
0x065c9d…c394
4 touches
1 conflict
0x9aee5419…1c82
0x065c9d…c394
4 touches
1 conflict
0xa4f4d1f2…0d52
0x065c9d…c394
4 touches
1 conflict
0xc744f3e4…e5b1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
2 touches
0 conflicts
0x5b571ba0…f13a
0x98dc6e…8633
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 0x0fd4b7e7c0…e504ee
Audit this contract →
← previous block·next block →recent activity