← previous blocknext block →recent activity
Analyzing
Block #86,668,247
33 transactions · 23 stateful · 2026-07-09 17:30:51 UTC
Parallelism
91/100
Blocked
39%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,668,247 · 33 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w013w015w016w117w218w223w024w125w127w228w230w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x2b3af004…e143
0x34b655…2a6f
4 touches
1 conflict
0x31c8d3fc…7559
0x34b655…2a6f
4 touches
1 conflict
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x7b3da897…b268
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0x82fbdeba…e163
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity