← previous blocknext block →recent activity
Analyzing
Block #87,738,410
55 transactions · 45 stateful · 2026-07-14 16:46:14 UTC
Parallelism
71/100
Blocked
67%
Avg conflicts / tx
2.15
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,738,410 · 55 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
3w06w17w08w19w210w311w412w013w114w015w116w218w019w220w321w425w526w627w737w141w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x9001f549…089d
0x34b655…2a6f
16 touches
28 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
14 touches
21 conflicts
0x58620f29…db5a
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
14 touches
21 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
14 touches
21 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity