← previous blocknext block →recent activity
Analyzing
Block #76,195,690
7 transactions · 6 stateful · 2026-05-22 05:13:37 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,195,690 · 7 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
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05ef41a5…4f30
0x065c9d…c394
2 touches
0 conflicts
0x5b9181d9…d9e2
0x065c9d…c394
2 touches
0 conflicts
0x74f859ad…5226
0x065c9d…c394
2 touches
0 conflicts
0x7e5b802f…0b92
0x065c9d…c394
2 touches
0 conflicts
0xcce31644…7514
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity