← previous blocknext block →recent activity
Analyzing
Block #99,492,410
21 transactions · 20 stateful · 2026-08-27 02:11:32 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,492,410 · 21 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
1w02w13w24w05w17w011w113w214w115w216w217w318w419w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39faf6fe…d786
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x88b8a8b4…5e9b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xdc0a13af…120c
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
0x34b655…2a6f
6 touches
3 conflicts
0x19004998…6d2c
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x39faf6fe9b…3bd786
Audit this contract →
← previous block·next block →recent activity