← previous blocknext block →recent activity
Analyzing
Block #86,257,058
22 transactions · 18 stateful · 2026-07-07 19:40:49 UTC
Parallelism
73/100
Blocked
39%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,257,058 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w210w011w116w317w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
6 touches
3 conflicts
0xe732567d…b65d
0x34b655…2a6f
6 touches
3 conflicts
0xe9452241…95a3
0x34b655…2a6f
6 touches
3 conflicts
0xc03846bb…73b3
0x34b655…2a6f
6 touches
3 conflicts
0xef17b8cd…9511
0x34b655…2a6f
6 touches
3 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
6 touches
3 conflicts
0xb05fd028…2b45
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity