← previous blocknext block →recent activity
Analyzing
Block #86,795,326
26 transactions · 20 stateful · 2026-07-10 07:39:25 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,795,326 · 26 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
1w02w13w27w212w013w116w017w018w119w220w321w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xe7f9115e…e7bc
0x34b655…2a6f
6 touches
3 conflicts
0xf8daa076…a120
0x34b655…2a6f
6 touches
3 conflicts
0xf8daa076…a121
0x34b655…2a6f
6 touches
3 conflicts
0x37d6b7c1…3cce
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
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: Perpl
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity