← previous blocknext block →recent activity
Analyzing
Block #87,718,213
60 transactions · 48 stateful · 2026-07-14 14:31:09 UTC
Parallelism
67/100
Blocked
69%
Avg conflicts / tx
2.72
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #87,718,213 · 60 txs across 20 waves · depth 20
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
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w08w19w210w111w012w113w220w121w235w336w439w1342w1445w155w1656w1758w19
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x8b818135…eff8
0x34b655…2a6f
18 touches
36 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x13510de3…1c68
0x34b655…2a6f
10 touches
10 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
10 touches
10 conflicts
0x5f234b05…db39
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity