← previous blocknext block →recent activity
Analyzing
Block #98,286,532
14 transactions · 13 stateful · 2026-08-22 20:20:32 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,286,532 · 14 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
1w02w13w24w09w310w011w112w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92664c6e…e3ca
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7158e7f2…fabf
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x3e04662b…0da1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0007
0x340143…768f
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 0x92664c6e68…75e3ca
Audit this contract →
← previous block·next block →recent activity