← previous blocknext block →recent activity
Analyzing
Block #87,596,280
59 transactions · 39 stateful · 2026-07-14 00:55:38 UTC
Parallelism
73/100
Blocked
72%
Avg conflicts / tx
1.97
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,596,280 · 59 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
2w03w14w05w111w012w125w226w327w428w529w630w731w832w933w1034w1138w641w142w244w245w346w447w548w350w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…003d
0x40c49f…2af0
12 touches
15 conflicts
0xb8431b57…6825
0x34b655…2a6f
10 touches
10 conflicts
0x48719cbe…5484
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x26050074…6967
0x34b655…2a6f
8 touches
6 conflicts
0x36890fff…f3d1
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity