← previous blocknext block →recent activity
Analyzing
Block #86,491,207
21 transactions · 19 stateful · 2026-07-08 21:45:07 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,491,207 · 21 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
1w03w15w07w08w19w211w213w114w215w318w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa584fb3d…c78d
0x34b655…2a6f
6 touches
3 conflicts
0x080ec687…da80
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x452f2538…1cfc
0x34b655…2a6f
4 touches
1 conflict
0x68e52406…3352
0x34b655…2a6f
4 touches
1 conflict
0xb624d2ea…8c87
0x34b655…2a6f
4 touches
1 conflict
0xd6d040d9…9ae3
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 0xa584fb3de9…f0c78d
Audit this contract →
← previous block·next block →recent activity