← previous blocknext block →recent activity
Analyzing
Block #77,182,091
15 transactions · 15 stateful · 2026-05-26 18:41:06 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #77,182,091 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w39w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x77ed432f…fa04
0x065c9d…c394
10 touches
10 conflicts
0x95523e2a…4c01
0x065c9d…c394
8 touches
6 conflicts
0x06e40499…165e
0x1d1325…2305
4 touches
1 conflict
0x45f562b2…9294
0x1d1325…2305
4 touches
1 conflict
0x8488f10f…9353
0x1d1325…2305
4 touches
1 conflict
0x8488f10f…9354
0x1d1325…2305
4 touches
1 conflict
0x8488f10f…9355
0x1d1325…2305
4 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity