← previous blocknext block →recent activity
Analyzing
Block #77,349,244
10 transactions · 7 stateful · 2026-05-27 13:18:01 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,349,244 · 10 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xefb2b6ae…1790
0x065c9d…c394
3 touches
1 conflict
0x51578e34…c299
0x065c9d…c394
3 touches
1 conflict
0x4a6e0905…76ee
0x065c9d…c394
2 touches
0 conflicts
0x57265ecc…70a7
0x065c9d…c394
2 touches
0 conflicts
0x85f9caef…2119
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 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity