← previous blocknext block →recent activity
Analyzing
Block #85,921,130
32 transactions · 22 stateful · 2026-07-06 06:18:07 UTC
Parallelism
88/100
Blocked
50%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,921,130 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w211w012w113w216w017w119w020w221w123w324w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda6b535e…6d68
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0xa20a130c…5d59
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 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: ShMonad (shMON)
3 conflicts on slot 0xda6b535e6c…386d68
Audit this contract →
← previous block·next block →recent activity