← previous blocknext block →recent activity
Analyzing
Block #87,595,515
13 transactions · 11 stateful · 2026-07-14 00:50:30 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,595,515 · 13 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
1w02w13w26w07w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x7527802e…2ba9
0x34b655…2a6f
8 touches
6 conflicts
0x0f00f2df…7579
0x34b655…2a6f
6 touches
3 conflicts
0x105e7432…03f4
0x34b655…2a6f
6 touches
3 conflicts
0x18904470…0ef9
0x34b655…2a6f
6 touches
3 conflicts
0x21158693…63e2
0x34b655…2a6f
6 touches
3 conflicts
0x40c2d677…f53a
0x34b655…2a6f
6 touches
3 conflicts
0x4493e999…dae9
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity