← previous blocknext block →recent activity
Analyzing
Block #87,714,458
40 transactions · 35 stateful · 2026-07-14 14:05:54 UTC
Parallelism
60/100
Blocked
74%
Avg conflicts / tx
3.95
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,714,458 · 40 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w37w08w09w113w114w215w316w431w732w833w1334w1435w336w1538w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
10 touches
10 conflicts
0xa6389d47…9a28
0x34b655…2a6f
10 touches
10 conflicts
0xdb529f62…663c
0x34b655…2a6f
10 touches
10 conflicts
0x70e3da66…674a
0x34b655…2a6f
10 touches
10 conflicts
0x1aa5ecc1…1b3d
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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity