← previous blocknext block →recent activity
Analyzing
Block #86,844,260
16 transactions · 15 stateful · 2026-07-10 13:06:42 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,844,260 · 16 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
2w03w14w25w38w415w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7babfe9a…ff96
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x0ee5f19f…84fa
0x34b655…2a6f
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x9b982dcd…3dd9
0x34b655…2a6f
4 touches
1 conflict
0xa07e7b13…7513
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
6 conflicts on slot 0x7babfe9a22…93ff96
Audit this contract →
← previous block·next block →recent activity