← previous blocknext block →recent activity
Analyzing
Block #77,354,919
21 transactions · 17 stateful · 2026-05-27 13:55:46 UTC
Parallelism
90/100
Blocked
12%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,354,919 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5280e20b…d708
0xd32edf…ff58
3 touches
1 conflict
0x1b1b24af…a1b5
0x065c9d…c394
2 touches
0 conflicts
0x2998b753…e351
0x065c9d…c394
2 touches
0 conflicts
0x2eb0dff5…b250
0x065c9d…c394
2 touches
0 conflicts
0x6f707266…2186
0x065c9d…c394
2 touches
0 conflicts
0x7f50612c…11fd
0x065c9d…c394
2 touches
0 conflicts
0xa261169f…a713
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity