← previous blocknext block →recent activity
Analyzing
Block #77,261,075
13 transactions · 10 stateful · 2026-05-27 03:30:56 UTC
Parallelism
62/100
Blocked
40%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #77,261,075 · 13 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
1w02w05w16w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x8b2dcbe3…660c
0x065c9d…c394
4 touches
1 conflict
0x2adb670c…0b83
0x065c9d…c394
3 touches
1 conflict
0xd3b14a75…43c9
0x065c9d…c394
3 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
3 conflicts on slot 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity