← previous blocknext block →recent activity
Analyzing
Block #87,737,165
28 transactions · 27 stateful · 2026-07-14 16:37:54 UTC
Parallelism
43/100
Blocked
74%
Avg conflicts / tx
5
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,737,165 · 28 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
2w03w14w25w36w47w58w69w710w811w912w1013w1114w1215w1316w1418w119w220w324w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
32 touches
120 conflicts
0x9001f549…089d
0x34b655…2a6f
26 touches
78 conflicts
0x5b145de0…367c
0xc8689a…ee79
24 touches
66 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
24 touches
66 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
24 touches
66 conflicts
0x58620f29…db5a
0x34b655…2a6f
24 touches
66 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
24 touches
66 conflicts
0x2e283bef…e2c0
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
120 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity