← previous blocknext block →recent activity
Analyzing
Block #86,817,823
13 transactions · 11 stateful · 2026-07-10 10:09:47 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,817,823 · 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
5w06w17w09w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6976870…db3b
0x34b655…2a6f
4 touches
1 conflict
0xf83b23f9…5a2e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xf83b23f9…5a2f
0x34b655…2a6f
4 touches
1 conflict
0x21aef675…a95c
0x34b655…2a6f
4 touches
1 conflict
0x39a9cff1…0bd8
0x34b655…2a6f
4 touches
1 conflict
0x182656ab…3ff0
0x851145…3f07
4 touches
1 conflict
0x833d2d11…e7ba
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
1 conflict on slot 0xf6976870a9…21db3b
Audit this contract →
← previous block·next block →recent activity