← previous blocknext block →recent activity
Analyzing
Block #86,316,668
16 transactions · 11 stateful · 2026-07-08 02:18:43 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,316,668 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w113w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2de0f6…e6c6
0x34b655…2a6f
4 touches
1 conflict
0x5cb4c74e…381e
0x34b655…2a6f
4 touches
1 conflict
0x5cb4c74e…381f
0x34b655…2a6f
4 touches
1 conflict
0xa247054d…01de
0x34b655…2a6f
4 touches
1 conflict
0xcb89a818…e7c1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0f9089d5…c199
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 0x0d2de0f636…8fe6c6
Audit this contract →
← previous block·next block →recent activity