← previous blocknext block →recent activity
Analyzing
Block #86,656,785
9 transactions · 7 stateful · 2026-07-09 16:14:22 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,656,785 · 9 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
1w02w13w04w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6183ee9a…21b1
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x6c68ddc9…d106
0xb1dbf0…c0d3
4 touches
1 conflict
0xfaf89f45…ced6
0x34b655…2a6f
2 touches
0 conflicts
0xfefb0189…f726
0x34b655…2a6f
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity