← previous blocknext block →recent activity
Analyzing
Block #87,729,926
25 transactions · 23 stateful · 2026-07-14 15:49:29 UTC
Parallelism
24/100
Blocked
78%
Avg conflicts / tx
6.8
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,729,926 · 25 txs across 19 waves · depth 19
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
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w710w811w912w1013w1114w1215w1316w1417w1518w1619w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
36 touches
153 conflicts
0x67905f6e…02a1
0x34b655…2a6f
36 touches
153 conflicts
0x5b145de0…367c
0xc8689a…ee79
34 touches
136 conflicts
0x4ca1448c…9de6
0x34b655…2a6f
34 touches
136 conflicts
0x2f461725…5ab2
0x34b655…2a6f
34 touches
136 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
34 touches
136 conflicts
0x312e4698…54c0
0x34b655…2a6f
34 touches
136 conflicts
0x77830e75…7f31
0x34b655…2a6f
16 touches
28 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
153 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity