← previous blocknext block →recent activity
Analyzing
Block #87,490,170
16 transactions · 15 stateful · 2026-07-13 13:05:06 UTC
Parallelism
50/100
Blocked
47%
Avg conflicts / tx
1.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,490,170 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w38w49w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x5b33f5b9…4bab
0x34b655…2a6f
10 touches
10 conflicts
0x4fcdfbf8…56d0
0x34b655…2a6f
8 touches
6 conflicts
0x7cb1d883…dc23
0x34b655…2a6f
8 touches
6 conflicts
0x379a4b76…556c
0x34b655…2a6f
6 touches
3 conflicts
0x5ad1e512…4740
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x68c6f45f…9d1d
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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity