← previous blocknext block →recent activity
Analyzing
Block #99,481,105
26 transactions · 26 stateful · 2026-08-27 01:14:36 UTC
Parallelism
81/100
Blocked
58%
Avg conflicts / tx
1.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,481,105 · 26 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
1w02w13w24w05w16w17w19w010w111w212w314w317w219w420w221w222w425w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd9722304…6ed0
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x8f833b95…a78e
0xd32edf…ff58
7 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
4 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x25da5e59…fee6
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity