← previous blocknext block →recent activity
Analyzing
Block #87,524,510
68 transactions · 56 stateful · 2026-07-13 16:55:27 UTC
Parallelism
72/100
Blocked
71%
Avg conflicts / tx
2.46
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,524,510 · 68 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w18w211w012w113w214w322w423w529w538w340w441w142w851w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0xc36fa358…24cb
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0001
0xc1ff9f…b0fc
14 touches
21 conflicts
0x0733be30…112f
0x34b655…2a6f
14 touches
21 conflicts
0x71806e15…2893
0x34b655…2a6f
14 touches
21 conflicts
0x737acb78…fce8
0x34b655…2a6f
14 touches
21 conflicts
0xe8352ac7…d7a3
0x34b655…2a6f
12 touches
15 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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity