← previous blocknext block →recent activity
Analyzing
Block #87,456,691
14 transactions · 11 stateful · 2026-07-13 09:21:16 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,456,691 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w09w310w412w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x11d629eb…bcd9
0x34b655…2a6f
4 touches
1 conflict
0x694bf0dd…d36b
0x34b655…2a6f
4 touches
1 conflict
0x6a07f9d4…c440
0x34b655…2a6f
4 touches
1 conflict
0x767799cd…f423
0xc8689a…ee79
4 touches
1 conflict
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