← previous blocknext block →recent activity
Analyzing
Block #86,353,838
18 transactions · 11 stateful · 2026-07-08 06:26:55 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,353,838 · 18 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
2w06w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ea6a117…f2f2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x0cfc5c41…0986
0x34b655…2a6f
3 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x342fbbca…d443
0x40c49f…2af0
2 touches
0 conflicts
0x43a3af78…f8bf
0x40c49f…2af0
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 0x7ea6a11745…1df2f2
Audit this contract →
← previous block·next block →recent activity