← previous blocknext block →recent activity
Analyzing
Block #77,491,051
15 transactions · 11 stateful · 2026-05-28 05:02:43 UTC
Parallelism
87/100
Blocked
9%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,491,051 · 15 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
1w02w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9a93cba8…d78b
0x065c9d…c394
3 touches
1 conflict
0x3db31783…ef00
0x065c9d…c394
3 touches
1 conflict
0x095f112d…8eaf
0x065c9d…c394
2 touches
0 conflicts
0x58aaa1f9…008d
0x065c9d…c394
2 touches
0 conflicts
0x9083008a…cfd1
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
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
1 conflict on slot 0xce827910a4…82ff22
Audit this contract →
← previous block·next block →recent activity