← previous blocknext block →recent activity
Analyzing
Block #86,855,913
22 transactions · 20 stateful · 2026-07-10 14:24:35 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,855,913 · 22 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
5w06w17w29w110w313w417w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x27efc41a…dc7a
0x34b655…2a6f
6 touches
3 conflicts
0xa11d1ff5…7f7e
0x34b655…2a6f
6 touches
3 conflicts
0xc58a456f…3e3d
0x34b655…2a6f
6 touches
3 conflicts
0xc70dd80f…d075
0x34b655…2a6f
6 touches
3 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
6 touches
3 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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity