← previous blocknext block →recent activity
Analyzing
Block #86,664,160
20 transactions · 17 stateful · 2026-07-09 17:03:35 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,664,160 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w210w011w113w214w015w116w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x814f0f40…c654
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x1a843f41…02aa
0x34b655…2a6f
4 touches
1 conflict
0x1d50af5e…224d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53f5d89a…6ee4
0x34b655…2a6f
4 touches
1 conflict
0x660c9d95…7859
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
3 conflicts on slot 0x814f0f40f3…5dc654
Audit this contract →
← previous block·next block →recent activity