← previous blocknext block →recent activity
Analyzing
Block #87,578,399
20 transactions · 18 stateful · 2026-07-13 22:56:01 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,578,399 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w510w011w115w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07f69062…03ec
0x34b655…2a6f
8 touches
6 conflicts
0x1ee4a6d2…6389
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa4b200a3…2de6
0x34b655…2a6f
6 touches
3 conflicts
0xd026fe03…7748
0x34b655…2a6f
6 touches
3 conflicts
0x6834ce23…a96c
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 0x07f6906240…ea03ec
Audit this contract →
← previous block·next block →recent activity