← previous blocknext block →recent activity
Analyzing
Block #92,810,655
15 transactions · 14 stateful · 2026-08-03 15:29:18 UTC
Parallelism
40/100
Blocked
64%
Avg conflicts / tx
1.33
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #92,810,655 · 15 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w48w59w611w712w813w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab5ba139…ea6f
0x34b655…2a6f
10 touches
10 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xee8b5a0a…f8a6
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x9fa1409b…0e56
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3d93ad2c…e747
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
10 conflicts on slot 0xab5ba139f3…9fea6f
Audit this contract →
← previous block·next block →recent activity