← previous blocknext block →recent activity
Analyzing
Block #76,239,185
9 transactions · 6 stateful · 2026-05-22 10:03:31 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,239,185 · 9 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
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbb1010b8…84e5
0x065c9d…c394
4 touches
1 conflict
0xab6f429c…21c1
0x065c9d…c394
3 touches
1 conflict
0x5853b1db…7bcd
0x065c9d…c394
2 touches
0 conflicts
0x5e03d9b0…e783
0x065c9d…c394
2 touches
0 conflicts
0x7623bba2…c0df
0x065c9d…c394
2 touches
0 conflicts
0xca985cea…a40d
0x065c9d…c394
2 touches
0 conflicts
0xd0d8d9bb…e35c
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