← previous blocknext block →recent activity
Analyzing
Block #86,506,858
12 transactions · 11 stateful · 2026-07-08 23:29:29 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,506,858 · 12 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c16a1d9…0d51
0x34b655…2a6f
4 touches
1 conflict
0x98d31f6b…5804
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x70b87e4d…65d5
0x34b655…2a6f
4 touches
1 conflict
0xb428493a…2ee5
0x34b655…2a6f
4 touches
1 conflict
0xd5b06032…7fb8
0x34b655…2a6f
4 touches
1 conflict
0xe727ab72…768b
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
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 0x4c16a1d991…6a0d51
Audit this contract →
← previous block·next block →recent activity