← previous blocknext block →recent activity
Analyzing
Block #87,616,555
16 transactions · 13 stateful · 2026-07-14 03:11:12 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,616,555 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w38w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83b2a37e…eb5d
0x34b655…2a6f
6 touches
3 conflicts
0xa243ce39…3ff4
0x34b655…2a6f
6 touches
3 conflicts
0xa5ab7b8a…c97b
0x34b655…2a6f
6 touches
3 conflicts
0xb95e925b…392d
0x34b655…2a6f
6 touches
3 conflicts
0xba639250…76be
0x34b655…2a6f
6 touches
3 conflicts
0x207b4a17…4084
0x34b655…2a6f
6 touches
3 conflicts
0xec144908…8d17
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
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 0x83b2a37e74…9deb5d
Audit this contract →
← previous block·next block →recent activity