← previous blocknext block →recent activity
Analyzing
Block #87,737,995
20 transactions · 18 stateful · 2026-07-14 16:43:27 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,737,995 · 20 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
1w02w14w26w08w110w211w313w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x2b7950c1…2342
0x34b655…2a6f
10 touches
10 conflicts
0x7048d42f…288b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0003
0x0d73bf…be07
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x10e7709d…4090
0x34b655…2a6f
4 touches
1 conflict
0x10e7709d…4091
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
10 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity