← previous blocknext block →recent activity
Analyzing
Block #87,499,037
20 transactions · 18 stateful · 2026-07-13 14:04:26 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,499,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
1w02w03w15w06w17w28w310w111w212w313w014w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xe20a9313…c20a
0x34b655…2a6f
8 touches
6 conflicts
0x35075a55…56b4
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x6b2ba712…0214
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0x015c28a0…37da
0x34b655…2a6f
6 touches
3 conflicts
0x18e37e7d…bab2
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity