← previous blocknext block →recent activity
Analyzing
Block #87,727,529
49 transactions · 39 stateful · 2026-07-14 15:33:28 UTC
Parallelism
63/100
Blocked
69%
Avg conflicts / tx
2.22
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,727,529 · 49 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w29w010w111w219w120w321w422w523w628w929w1030w1133w1234w1343w1444w1545w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
14 touches
21 conflicts
0x0363d65e…06d2
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xafb8e71e…9285
0x34b655…2a6f
12 touches
15 conflicts
0x8218911e…3bed
0x34b655…2a6f
12 touches
15 conflicts
0x9eb101e5…003f
0x34b655…2a6f
10 touches
10 conflicts
0x99c5409a…25b7
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
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
21 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity