← previous blocknext block →recent activity
Analyzing
Block #76,483,006
13 transactions · 12 stateful · 2026-05-23 13:06:46 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,483,006 · 13 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
0x7ac9bc76…fec5
0x065c9d…c394
4 touches
1 conflict
0xdeb7e782…5f1b
0x065c9d…c394
3 touches
1 conflict
0x761409e6…7456
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x379df9e2…56d8
0x065c9d…c394
2 touches
0 conflicts
0x6c3a3837…4fb1
0x065c9d…c394
2 touches
0 conflicts
0xc582b707…8315
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 0x7ac9bc76bf…c2fec5
Audit this contract →
← previous block·next block →recent activity