← previous blocknext block →recent activity
Analyzing
Block #86,299,994
30 transactions · 28 stateful · 2026-07-08 00:27:15 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,299,994 · 30 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
1w02w13w211w012w113w014w115w220w221w022w024w125w327w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d9867ad…6d9a
0x34b655…2a6f
6 touches
3 conflicts
0x5a36b1f8…14f6
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
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 0x1d9867ade5…7b6d9a
Audit this contract →
← previous block·next block →recent activity