← previous blocknext block →recent activity
Analyzing
Block #99,354,643
25 transactions · 25 stateful · 2026-08-26 14:37:39 UTC
Parallelism
72/100
Blocked
52%
Avg conflicts / tx
1.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,354,643 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w58w09w111w012w115w216w319w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70e677f5…e3bd
0x34b655…2a6f
12 touches
15 conflicts
0xea8ba8ba…d967
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x84611dd3…b346
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
15 conflicts on slot 0x70e677f5c0…90e3bd
Audit this contract →
← previous block·next block →recent activity