← previous blocknext block →recent activity
Analyzing
Block #86,983,091
17 transactions · 16 stateful · 2026-07-11 04:34:37 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.12
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,983,091 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w08w110w211w414w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e942750…9953
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5fee1ba0…2520
0x34b655…2a6f
8 touches
6 conflicts
0x7da56943…9753
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xbfdd8306…fa07
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
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 0x6e9427506e…729953
Audit this contract →
← previous block·next block →recent activity