← previous blocknext block →recent activity
Analyzing
Block #77,350,758
17 transactions · 12 stateful · 2026-05-27 13:28:04 UTC
Parallelism
82/100
Blocked
17%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,350,758 · 17 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x528062b7…c00f
0x065c9d…c394
3 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x47f375d7…6e65
0x065c9d…c394
2 touches
0 conflicts
0x550fe940…e6d8
0x065c9d…c394
2 touches
0 conflicts
0x5d89e466…b8b6
0x065c9d…c394
2 touches
0 conflicts
0x70073345…8836
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