← previous blocknext block →recent activity
Analyzing
Block #87,736,048
21 transactions · 21 stateful · 2026-07-14 16:30:26 UTC
Parallelism
71/100
Blocked
62%
Avg conflicts / tx
1.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,736,048 · 21 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
1w02w13w14w25w36w07w19w210w311w413w314w516w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x4b49ff72…7d0f
0xd32edf…ff58
7 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x8ca13937…b3ce
0x34b655…2a6f
6 touches
3 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
10 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity