← previous blocknext block →recent activity
Analyzing
Block #92,311,670
12 transactions · 12 stateful · 2026-08-01 21:38:26 UTC
Parallelism
58/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,311,670 · 12 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
1w02w13w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02991b41…19e6
0x34b655…2a6f
6 touches
3 conflicts
0x244ad313…b4e5
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x91220b8f…7a02
0x1b6862…e19c
4 touches
1 conflict
0x9157a62a…cf7a
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x02991b41c5…1a19e6
Audit this contract →
← previous block·next block →recent activity