← previous blocknext block →recent activity
Analyzing
Block #86,702,380
18 transactions · 16 stateful · 2026-07-09 21:18:39 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,702,380 · 18 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
6w07w010w111w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x044844a0…7418
0x34b655…2a6f
4 touches
1 conflict
0x1ae4eefc…ccee
0x34b655…2a6f
4 touches
1 conflict
0x26dee23d…b18b
0x34b655…2a6f
4 touches
1 conflict
0x2e641595…ce8d
0x34b655…2a6f
4 touches
1 conflict
0x30533e7b…5e0f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4b2b1640…1bb8
0x34b655…2a6f
4 touches
1 conflict
0x6153fb59…b910
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
1 conflict on slot 0x044844a0f0…d07418
Audit this contract →
← previous block·next block →recent activity