← previous blocknext block →recent activity
Analyzing
Block #87,708,877
42 transactions · 37 stateful · 2026-07-14 13:28:31 UTC
Parallelism
57/100
Blocked
59%
Avg conflicts / tx
2.43
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,708,877 · 42 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w17w08w19w210w311w412w513w614w715w817w918w1022w1225w1329w1430w1532w1634w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x4560e5a8…b741
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x8b818135…eff8
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x3f50346c…0a88
0x34b655…2a6f
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity