← previous blocknext block →recent activity
Analyzing
Block #87,615,306
35 transactions · 31 stateful · 2026-07-14 03:02:50 UTC
Parallelism
54/100
Blocked
74%
Avg conflicts / tx
2.4
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,615,306 · 35 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w18w09w110w211w312w215w316w417w518w619w720w821w922w1027w1328w229w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
12 touches
15 conflicts
0x19e9a11b…e981
0x34b655…2a6f
8 touches
6 conflicts
0x25329a48…4e00
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0001
0xc1ff9f…b0fc
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x68b75835…d6f3
0x34b655…2a6f
8 touches
6 conflicts
0x79e62da8…efdc
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity