← previous blocknext block →recent activity
Analyzing
Block #87,588,670
48 transactions · 36 stateful · 2026-07-14 00:04:42 UTC
Parallelism
73/100
Blocked
64%
Avg conflicts / tx
1.27
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,588,670 · 48 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w212w013w114w016w117w218w319w420w221w322w423w524w627w930w1035w246w147w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0001
0xc1ff9f…b0fc
10 touches
10 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
8 touches
6 conflicts
0xe9452241…95a3
0x34b655…2a6f
8 touches
6 conflicts
0x3c4b8fbd…9354
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7bc81c3e…54a2
0x34b655…2a6f
6 touches
3 conflicts
0x8d68898d…ab1d
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity