← previous blocknext block →recent activity
Analyzing
Block #86,776,363
18 transactions · 14 stateful · 2026-07-10 05:32:54 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,776,363 · 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
2w06w17w08w19w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa37e64f8…ba05
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x8212e232…180e
0x34b655…2a6f
4 touches
1 conflict
0x9cbe5c47…424b
0x34b655…2a6f
4 touches
1 conflict
0xb784e5ed…fb82
0x34b655…2a6f
4 touches
1 conflict
0xe5acefce…a322
0x34b655…2a6f
4 touches
1 conflict
0xfa440e84…21da
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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
3 conflicts on slot 0xa37e64f8b9…21ba05
Audit this contract →
← previous block·next block →recent activity