← previous blocknext block →recent activity
Analyzing
Block #86,957,866
14 transactions · 13 stateful · 2026-07-11 01:46:04 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,957,866 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w39w410w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b7950c1…2342
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xb07a0849…3b62
0xb1dbf0…c0d3
4 touches
1 conflict
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0xc2ebcc0c…2261
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x2b7950c182…352342
Audit this contract →
← previous block·next block →recent activity