← previous blocknext block →recent activity
Analyzing
Block #87,409,409
32 transactions · 31 stateful · 2026-07-13 04:05:06 UTC
Parallelism
47/100
Blocked
61%
Avg conflicts / tx
2.81
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,409,409 · 32 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w17w28w39w410w511w614w715w816w918w119w1021w225w1129w1530w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801058a8…5bc3
0x34b655…2a6f
18 touches
36 conflicts
0x05a7428b…ddf3
0x34b655…2a6f
18 touches
36 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0x326a02b5…8dad
0x34b655…2a6f
14 touches
21 conflicts
0x086db8fc…0024
0x34b655…2a6f
14 touches
21 conflicts
0x286711a5…b3bf
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x1951ee47…540f
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
36 conflicts on slot 0x801058a816…5a5bc3
Audit this contract →
← previous block·next block →recent activity