← previous blocknext block →recent activity
Analyzing
Block #86,846,799
22 transactions · 17 stateful · 2026-07-10 13:23:37 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,846,799 · 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
1w04w05w19w010w211w312w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xa6ca03ef…80e4
0x34b655…2a6f
6 touches
3 conflicts
0xb4c0ff71…082d
0x34b655…2a6f
4 touches
1 conflict
0xb920dba4…4826
0x34b655…2a6f
4 touches
1 conflict
0xad676684…c58b
0x754704…b603
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity