← previous blocknext block →recent activity
Analyzing
Block #86,666,917
27 transactions · 21 stateful · 2026-07-09 17:21:58 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,666,917 · 27 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
1w02w13w14w25w26w07w110w011w114w217w324w425w526w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8eb0ac6b…a73a
0x34b655…2a6f
10 touches
10 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
8 touches
6 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
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 0x8eb0ac6bf2…4da73a
Audit this contract →
← previous block·next block →recent activity