← previous blocknext block →recent activity
Analyzing
Block #87,717,029
18 transactions · 17 stateful · 2026-07-14 14:23:13 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,717,029 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w310w411w513w614w016w617w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7525206c…fbd5
0x34b655…2a6f
10 touches
10 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x722851f4…73fe
0x34b655…2a6f
6 touches
3 conflicts
0x7f1ff409…9042
0x34b655…2a6f
4 touches
1 conflict
0xc61a83f6…7a98
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 0x7525206cf5…dcfbd5
Audit this contract →
← previous block·next block →recent activity