← previous blocknext block →recent activity
Analyzing
Block #86,335,639
16 transactions · 12 stateful · 2026-07-08 04:25:26 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,335,639 · 16 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
5w08w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bd10f19…273b
0x34b655…2a6f
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0x96dd83e6…a507
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x17651a83…e39e
0x065c9d…c394
2 touches
0 conflicts
0x20a2e268…6e8c
0x065c9d…c394
2 touches
0 conflicts
0x38f3cac5…0aa5
0x065c9d…c394
2 touches
0 conflicts
0x7744efa5…312c
0x065c9d…c394
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 0x5bd10f1923…99273b
Audit this contract →
← previous block·next block →recent activity