← previous blocknext block →recent activity
Analyzing
Block #87,703,037
45 transactions · 35 stateful · 2026-07-14 12:49:22 UTC
Parallelism
69/100
Blocked
63%
Avg conflicts / tx
1.73
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,703,037 · 45 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w210w011w118w019w120w221w322w423w524w625w727w128w231w832w933w235w1037w1142w1244w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
10 touches
10 conflicts
0x2717d69b…b6f2
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity