← previous blocknext block →recent activity
Analyzing
Block #87,723,230
40 transactions · 31 stateful · 2026-07-14 15:04:41 UTC
Parallelism
63/100
Blocked
65%
Avg conflicts / tx
3.13
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,723,230 · 40 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w210w311w412w513w614w715w816w917w1018w1119w1220w1321w1429w430w532w636w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0xf4f4af3b…c5bd
0x34b655…2a6f
16 touches
28 conflicts
0x97c67486…27fe
0x34b655…2a6f
14 touches
21 conflicts
0xb11a3969…fc6a
0x34b655…2a6f
14 touches
21 conflicts
0x4ca81ae8…01d4
0x34b655…2a6f
14 touches
21 conflicts
0x6c2aa5be…d808
0x34b655…2a6f
14 touches
21 conflicts
0x5170a218…3a84
0xc8689a…ee79
14 touches
21 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
14 touches
21 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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity