← previous blocknext block →recent activity
Analyzing
Block #86,965,820
10 transactions · 8 stateful · 2026-07-11 02:39:15 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,965,820 · 10 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
0x1f1d2c6e…6b63
0x34b655…2a6f
4 touches
1 conflict
0x619281ca…b27d
0x34b655…2a6f
4 touches
1 conflict
0x1f1d2c6e…6b62
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3e6245ca…56c6
0x065c9d…c394
2 touches
0 conflicts
0x73b1c443…20b9
0x065c9d…c394
2 touches
0 conflicts
0x1299b030…e115
0x34b655…2a6f
2 touches
0 conflicts
0x1cb5e134…447d
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 0x1f1d2c6e43…886b63
Audit this contract →
← previous block·next block →recent activity