← previous blocknext block →recent activity
Analyzing
Block #76,462,804
11 transactions · 7 stateful · 2026-05-23 10:52:08 UTC
Parallelism
82/100
Blocked
14%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,462,804 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0xd9dae76a…e243
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x21dba876…61f5
0x065c9d…c394
2 touches
0 conflicts
0x2303d048…e611
0x065c9d…c394
2 touches
0 conflicts
0x66e739dc…d295
0x065c9d…c394
2 touches
0 conflicts
0xcf455ac7…99af
0x065c9d…c394
2 touches
0 conflicts
0xe6f4a326…ec4f
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 0x27a04273d4…7327c5
Audit this contract →
← previous block·next block →recent activity