← previous blocknext block →recent activity
Analyzing
Block #86,167,103
13 transactions · 11 stateful · 2026-07-07 09:40:00 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,167,103 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x65903ef9…2567
0x34b655…2a6f
2 touches
0 conflicts
0x9fff3d04…b5fd
0x34b655…2a6f
2 touches
0 conflicts
0xa29cba63…8030
0x34b655…2a6f
2 touches
0 conflicts
0xb91a6f59…722c
0x34b655…2a6f
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 0x3e6302c867…b164f5
Audit this contract →
← previous block·next block →recent activity