← previous blocknext block →recent activity
Analyzing
Block #85,147,137
17 transactions · 14 stateful · 2026-07-02 16:22:32 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,147,137 · 17 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
1w02w13w17w010w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26c0fbec…03eb
0x065c9d…c394
5 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xc3c642f4…e7b6
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0000
0x614b85…a284
2 touches
0 conflicts
0x00000000…0003
0x614b85…a284
2 touches
0 conflicts
0x00000000…0004
0x614b85…a284
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 0x26c0fbec99…6c03eb
Audit this contract →
← previous block·next block →recent activity