← previous blocknext block →recent activity
Analyzing
Block #77,237,717
12 transactions · 12 stateful · 2026-05-27 00:54:41 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,237,717 · 12 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
1w02w13w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x0c773e5b…9509
0x065c9d…c394
4 touches
1 conflict
0x0dcf62c8…556c
0x065c9d…c394
4 touches
1 conflict
0x0b570519…accc
0x065c9d…c394
3 touches
1 conflict
0x98761ee9…7e3b
0x065c9d…c394
3 touches
1 conflict
0xa28c3ff2…08ec
0x065c9d…c394
2 touches
0 conflicts
0xc405d5c6…33e4
0x065c9d…c394
2 touches
0 conflicts
0xe9a18eff…4d64
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity