← previous blocknext block →recent activity
Analyzing
Block #86,565,924
14 transactions · 10 stateful · 2026-07-09 06:04:53 UTC
Parallelism
71/100
Blocked
30%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,565,924 · 14 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
2w03w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1e48811e…2e39
0x34b655…2a6f
4 touches
1 conflict
0x4c04ce68…d007
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a4
0xb1dbf0…c0d3
4 touches
1 conflict
0x4af2cce5…16c4
0xb1dbf0…c0d3
3 touches
1 conflict
0xa28a039d…07d8
0x699abc…6a3b
2 touches
0 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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity