← previous blocknext block →recent activity
Analyzing
Block #87,870,037
20 transactions · 19 stateful · 2026-07-15 07:26:40 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,870,037 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w09w112w213w214w315w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x072c4867…c7a9
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x0d55d89d…a4ec
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
6 conflicts on slot 0x072c48676c…5bc7a9
Audit this contract →
← previous block·next block →recent activity