← previous blocknext block →recent activity
Analyzing
Block #87,729,111
48 transactions · 38 stateful · 2026-07-14 15:44:03 UTC
Parallelism
67/100
Blocked
71%
Avg conflicts / tx
2.13
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,729,111 · 48 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
1w02w13w05w18w09w111w012w113w014w116w218w119w220w321w422w523w624w725w826w927w1034w244w1345w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
10 touches
10 conflicts
0x9eb155db…f714
0x34b655…2a6f
10 touches
10 conflicts
0x32792f31…fc3e
0x34b655…2a6f
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x2c2761c0…476e
0x34b655…2a6f
8 touches
6 conflicts
0x2d7ea048…d78e
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity