← previous blocknext block →recent activity
Analyzing
Block #86,715,206
25 transactions · 20 stateful · 2026-07-09 22:44:15 UTC
Parallelism
72/100
Blocked
60%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,715,206 · 25 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
3w04w15w27w39w411w012w113w214w320w121w222w423w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0003
0x019883…2a9a
8 touches
6 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
8 touches
6 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
8 touches
6 conflicts
0x00000000…0000
0x019883…2a9a
8 touches
6 conflicts
0x00000000…0002
0x019883…2a9a
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity