← previous blocknext block →recent activity
Analyzing
Block #86,512,663
11 transactions · 11 stateful · 2026-07-09 00:08:11 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,512,663 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6827c800…a1a1
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x1e39996d…1c5c
0x40c49f…2af0
2 touches
0 conflicts
0x677e8872…cec0
0x40c49f…2af0
2 touches
0 conflicts
0xb2a762f1…e0d7
0x40c49f…2af0
2 touches
0 conflicts
0xf47ff7a3…64f4
0x40c49f…2af0
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 0x6827c80013…e0a1a1
Audit this contract →
← previous block·next block →recent activity