← previous blocknext block →recent activity
Analyzing
Block #87,584,079
53 transactions · 38 stateful · 2026-07-13 23:34:01 UTC
Parallelism
77/100
Blocked
68%
Avg conflicts / tx
1.75
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,584,079 · 53 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w27w314w015w118w019w124w025w126w230w331w432w537w338w641w742w343w444w547w648w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x5f34fd08…aeb3
0x34b655…2a6f
10 touches
10 conflicts
0x6827c800…a1a1
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x57bb625a…286d
0x34b655…2a6f
8 touches
6 conflicts
0x66f473d3…2d03
0xa6afd3…d132
8 touches
6 conflicts
0x7c6a17fa…e95d
0x34b655…2a6f
6 touches
3 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity