← previous blocknext block →recent activity
Analyzing
Block #87,408,087
30 transactions · 19 stateful · 2026-07-13 03:56:15 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,408,087 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w310w416w017w122w524w025w126w528w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d42dc8b…fdb6
0x2a68ba…90c5
8 touches
6 conflicts
0x2d7e6e2e…023b
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x78694995…f66e
0x1b6862…e19c
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x7d42dc8b22…fefdb6
Audit this contract →
← previous block·next block →recent activity