← previous blocknext block →recent activity
Analyzing
Block #99,456,517
26 transactions · 25 stateful · 2026-08-26 23:10:47 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.54
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,456,517 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w07w08w19w210w311w416w118w519w620w121w623w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x6adb14f2…877b
0xd32edf…ff58
9 touches
10 conflicts
0xbd590df7…9891
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x6fd9ae7c…e97d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity