← previous blocknext block →recent activity
Analyzing
Block #86,350,872
13 transactions · 12 stateful · 2026-07-08 06:07:07 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,350,872 · 13 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9365e097…ff56
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1ac8446d…69df
0x065c9d…c394
2 touches
0 conflicts
0x2d62c9c6…c7f8
0x065c9d…c394
2 touches
0 conflicts
0x3c253023…f3f0
0x065c9d…c394
2 touches
0 conflicts
0x3ea110a4…436d
0x065c9d…c394
2 touches
0 conflicts
0x473723a5…0c78
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 0x9365e0978e…fbff56
Audit this contract →
← previous block·next block →recent activity