← previous blocknext block →recent activity
Analyzing
Block #86,846,858
19 transactions · 15 stateful · 2026-07-10 13:24:01 UTC
Parallelism
84/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,846,858 · 19 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
1w02w16w07w08w19w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e0a3c1a…f9fb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xa4f86e8a…7166
0x34b655…2a6f
4 touches
1 conflict
0x8656a13f…f95e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x340f1d7e…84ef
0xd32edf…ff58
3 touches
1 conflict
0xba5743c7…21c2
0x1b6862…e19c
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: Perpl
1 conflict on slot 0x0e0a3c1a06…e6f9fb
Audit this contract →
← previous block·next block →recent activity