← previous blocknext block →recent activity
Analyzing
Block #99,959,498
24 transactions · 23 stateful · 2026-08-28 17:36:22 UTC
Parallelism
67/100
Blocked
65%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,959,498 · 24 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
1w02w13w24w05w06w17w28w310w012w113w214w315w416w317w118w520w222w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13857c98…0cc6
0x34b655…2a6f
10 touches
10 conflicts
0xb240b520…a88a
0x34b655…2a6f
10 touches
10 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0fc022c2…56d1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x13857c98dd…b70cc6
Audit this contract →
← previous block·next block →recent activity