← previous blocknext block →recent activity
Analyzing
Block #85,896,140
16 transactions · 14 stateful · 2026-07-06 03:31:39 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,896,140 · 16 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
1w02w13w111w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x394c3833…b4a7
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xbdc80bf7…e947
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x66c6a3df…a298
0x065c9d…c394
4 touches
1 conflict
0xc0a11fcc…5880
0x34b655…2a6f
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 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: ShMonad (shMON)
1 conflict on slot 0x394c38330b…c9b4a7
Audit this contract →
← previous block·next block →recent activity