← previous blocknext block →recent activity
Analyzing
Block #77,238,001
8 transactions · 8 stateful · 2026-05-27 00:56:35 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,238,001 · 8 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
1w03w14w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0xcf3abb99…888a
0x065c9d…c394
4 touches
1 conflict
0x802a56fd…c7d4
0x065c9d…c394
2 touches
0 conflicts
0x853c7f93…76dc
0x065c9d…c394
2 touches
0 conflicts
0x891d12ea…feac
0x065c9d…c394
2 touches
0 conflicts
0x912bf9f6…4dec
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