← previous blocknext block →recent activity
Analyzing
Block #86,454,955
20 transactions · 16 stateful · 2026-07-08 17:42:33 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,454,955 · 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
1w02w13w28w09w110w211w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x109d8a52…a7b7
0x34b655…2a6f
8 touches
6 conflicts
0x37d710c8…45c1
0x34b655…2a6f
8 touches
6 conflicts
0xd0ec9500…6194
0x34b655…2a6f
8 touches
6 conflicts
0x3230277c…ef39
0xc8689a…ee79
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xe1d1f14d…3ffb
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xbebeaa56…211b
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
6 conflicts on slot 0x109d8a5293…02a7b7
Audit this contract →
← previous block·next block →recent activity