← previous blocknext block →recent activity
Analyzing
Block #76,214,095
14 transactions · 10 stateful · 2026-05-22 07:16:01 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,214,095 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x1a78bc67…600d
0x065c9d…c394
2 touches
0 conflicts
0x6455f388…32c0
0x065c9d…c394
2 touches
0 conflicts
0x73151fe8…9514
0x065c9d…c394
2 touches
0 conflicts
0xda37f424…02d9
0x065c9d…c394
2 touches
0 conflicts
0xf5f27949…9541
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
3 conflicts on slot 0xf3d7a307cc…f14d63
Audit this contract →
← previous block·next block →recent activity