← previous blocknext block →recent activity
Analyzing
Block #86,669,653
28 transactions · 24 stateful · 2026-07-09 17:40:14 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,669,653 · 28 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
1w02w14w05w28w09w112w014w116w117w119w222w225w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0xbd7df4a4…efd7
0x065c9d…c394
5 touches
3 conflicts
0x1ba5d36c…9336
0x34b655…2a6f
4 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
4 touches
1 conflict
0x20bfcb14…4fd0
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity