← previous blocknext block →recent activity
Analyzing
Block #86,779,614
21 transactions · 14 stateful · 2026-07-10 05:54:35 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,779,614 · 21 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
2w07w08w112w014w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x19ba76c3…6342
0x34b655…2a6f
6 touches
3 conflicts
0x5ba51e87…44ee
0xb1dbf0…c0d3
4 touches
1 conflict
0xdbd174e4…b6f8
0x34b655…2a6f
4 touches
1 conflict
0x1509d2c8…8461
0x34b655…2a6f
4 touches
1 conflict
0x291ad0b4…69e9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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: Perpl
3 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity