← previous blocknext block →recent activity
Analyzing
Block #85,761,927
17 transactions · 15 stateful · 2026-07-05 12:37:43 UTC
Parallelism
76/100
Blocked
20%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,761,927 · 17 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
1w02w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8d386713…bc14
0x065c9d…c394
4 touches
1 conflict
0xee9a44d4…f37a
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x282691b4…5c00
0x065c9d…c394
3 touches
1 conflict
0x546f21f8…43cf
0x065c9d…c394
3 touches
1 conflict
0xe2263bea…6a9d
0x69df8a…6292
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity