← previous blocknext block →recent activity
Analyzing
Block #86,699,104
19 transactions · 18 stateful · 2026-07-09 20:56:46 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,699,104 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w49w510w615w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89c7ec3b…85ba
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x178457f9…d26a
0x34b655…2a6f
6 touches
3 conflicts
0x1bfc029c…f91e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0x63b15849…80b2
0x34b655…2a6f
6 touches
3 conflicts
0x70b87e4d…65d5
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x89c7ec3b6a…8e85ba
Audit this contract →
← previous block·next block →recent activity