← previous blocknext block →recent activity
Analyzing
Block #76,476,154
11 transactions · 10 stateful · 2026-05-23 12:21:07 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,476,154 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
8 touches
6 conflicts
0x27a04273…27c5
0x065c9d…c394
6 touches
3 conflicts
0x9d9abdfc…5b65
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2f88a23f…9dc5
0x2a68ba…90c5
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xffb1eb9c…4d56
0xd32edf…ff58
3 touches
1 conflict
0x18c9cf24…b14c
0x065c9d…c394
3 touches
1 conflict
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
6 conflicts on slot 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity