← previous blocknext block →recent activity
Analyzing
Block #77,357,801
19 transactions · 15 stateful · 2026-05-27 14:15:00 UTC
Parallelism
84/100
Blocked
20%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,357,801 · 19 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
2w03w112w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x94802d88…2062
0x065c9d…c394
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0xf682f47d…b34a
0x065c9d…c394
3 touches
1 conflict
0x9dfd359d…6a93
0x065c9d…c394
3 touches
1 conflict
0x54906aa0…efe6
0x065c9d…c394
3 touches
1 conflict
0x06e40499…165e
0x69df8a…6292
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity