← previous blocknext block →recent activity
Analyzing
Block #86,672,379
39 transactions · 31 stateful · 2026-07-09 17:58:27 UTC
Parallelism
64/100
Blocked
81%
Avg conflicts / tx
2.9
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #86,672,379 · 39 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w18w211w012w113w214w315w416w517w618w719w820w921w1022w1124w625w728w329w231w432w333w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x70ff9262…8d80
0x34b655…2a6f
10 touches
10 conflicts
0x0ff1ee46…0c08
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
10 touches
10 conflicts
0xac808a27…82db
0x34b655…2a6f
10 touches
10 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
8 touches
6 conflicts
0xcd22e5ab…739c
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity