← previous blocknext block →recent activity
Analyzing
Block #86,154,011
22 transactions · 16 stateful · 2026-07-07 08:12:39 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,154,011 · 22 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
1w02w15w06w27w08w115w116w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ba62008…95b8
0x40c49f…2af0
6 touches
3 conflicts
0xaed2c9df…5cec
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x1453931a…938f
0x065c9d…c394
5 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x382b3b57…a546
0x34b655…2a6f
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: 0x40c49f17…d22af0
3 conflicts on slot 0x3ba620084b…5095b8
Audit this contract →
← previous block·next block →recent activity