← previous blocknext block →recent activity
Analyzing
Block #99,356,160
33 transactions · 29 stateful · 2026-08-26 14:45:20 UTC
Parallelism
61/100
Blocked
72%
Avg conflicts / tx
1.85
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #99,356,160 · 33 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w37w48w09w410w511w112w613w417w719w120w323w424w525w530w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3c05624…3417
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x68531239…e9a3
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0xd3c0562470…3e3417
Audit this contract →
← previous block·next block →recent activity