← previous blocknext block →recent activity
Analyzing
Block #86,796,870
13 transactions · 11 stateful · 2026-07-10 07:49:45 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,796,870 · 13 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
1w04w06w17w08w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0b9f02c4…6fec
0x34b655…2a6f
4 touches
1 conflict
0x16f2b22d…d27f
0x34b655…2a6f
4 touches
1 conflict
0x20e68d2b…9954
0x34b655…2a6f
4 touches
1 conflict
0x21d72491…a535
0x34b655…2a6f
4 touches
1 conflict
0x268bd78a…7747
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity