← previous blocknext block →recent activity
Analyzing
Block #99,362,206
31 transactions · 30 stateful · 2026-08-26 15:15:51 UTC
Parallelism
84/100
Blocked
50%
Avg conflicts / tx
1.19
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,362,206 · 31 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
1w02w14w05w06w17w28w09w115w216w317w218w221w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02373c43…3cb3
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb482658a…e4f5
0x34b655…2a6f
8 touches
6 conflicts
0x5897e166…0a40
0xd32edf…ff58
7 touches
6 conflicts
0x6d43ee99…bdd9
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x9513aafb…bb7f
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
10 conflicts on slot 0x02373c432b…ff3cb3
Audit this contract →
← previous block·next block →recent activity