← previous blocknext block →recent activity
Analyzing
Block #86,805,360
12 transactions · 11 stateful · 2026-07-10 08:46:30 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,805,360 · 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
5w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6ed530e…fa7d
0x34b655…2a6f
4 touches
1 conflict
0x11d629eb…bcd9
0x34b655…2a6f
4 touches
1 conflict
0x8d888c90…5479
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0x02e673f3…9771
0x34b655…2a6f
2 touches
0 conflicts
0x093be39d…3e64
0x34b655…2a6f
2 touches
0 conflicts
0x14d5db25…1daf
0x34b655…2a6f
2 touches
0 conflicts
0x1e6d78c9…c1e1
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 0xc6ed530ecc…a9fa7d
Audit this contract →
← previous block·next block →recent activity