← previous blocknext block →recent activity
Analyzing
Block #76,396,532
6 transactions · 6 stateful · 2026-05-23 03:31:23 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,396,532 · 6 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dbd3f6c…30a0
0x065c9d…c394
3 touches
1 conflict
0x7d0c3724…499c
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1cb33c5a…ee2b
0x065c9d…c394
2 touches
0 conflicts
0x1d326f0f…4147
0x065c9d…c394
2 touches
0 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
2 touches
0 conflicts
0xdae4e105…00e4
0x065c9d…c394
2 touches
0 conflicts
0xde44e9b0…c720
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 0x9dbd3f6c1a…0730a0
Audit this contract →
← previous block·next block →recent activity