← previous blocknext block →recent activity
Analyzing
Block #87,318,031
16 transactions · 14 stateful · 2026-07-12 17:53:58 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,318,031 · 16 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
1w03w04w17w08w19w112w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c9eb6ea…7c39
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb9d523b4…9a21
0x34b655…2a6f
4 touches
1 conflict
0xe196aed0…324d
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfa4ac296…bace
0x34b655…2a6f
4 touches
1 conflict
0xfc7703e6…eefb
0x34b655…2a6f
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
3 conflicts on slot 0x0c9eb6ea19…6e7c39
Audit this contract →
← previous block·next block →recent activity