← previous blocknext block →recent activity
Analyzing
Block #77,349,180
8 transactions · 6 stateful · 2026-05-27 13:17:35 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,349,180 · 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
1w02w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xa857fd1a…99fb
0x065c9d…c394
4 touches
1 conflict
0x83a3d7aa…f6db
0x065c9d…c394
4 touches
1 conflict
0x5b111cc2…008e
0x065c9d…c394
4 touches
1 conflict
0x571d84a0…97b6
0x065c9d…c394
3 touches
1 conflict
0x06faf920…86e3
0x065c9d…c394
3 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
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 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity