← previous blocknext block →recent activity
Analyzing
Block #86,831,435
16 transactions · 13 stateful · 2026-07-10 11:40:58 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,831,435 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
6 touches
3 conflicts
0x2cd5aca1…0977
0x34b655…2a6f
6 touches
3 conflicts
0x8d888c90…5479
0x34b655…2a6f
4 touches
1 conflict
0x91aeebc1…093f
0x34b655…2a6f
4 touches
1 conflict
0x98862f54…62ca
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity