← previous blocknext block →recent activity
Analyzing
Block #76,482,631
12 transactions · 10 stateful · 2026-05-23 13:04:16 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,482,631 · 12 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
2w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x3d4cc54b…1525
0x065c9d…c394
4 touches
1 conflict
0x6a8e5263…0b4a
0x065c9d…c394
3 touches
1 conflict
0x3b15936c…2ee3
0x065c9d…c394
3 touches
1 conflict
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0c8ec6b9…cc32
0x065c9d…c394
2 touches
0 conflicts
0x18cf3003…51d1
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 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity