← previous blocknext block →recent activity
Analyzing
Block #99,308,200
18 transactions · 15 stateful · 2026-08-26 10:44:00 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,308,200 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w28w311w012w113w414w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
8 touches
6 conflicts
0x8b7fe709…9d99
0x34b655…2a6f
8 touches
6 conflicts
0xb0e974c4…b84d
0x34b655…2a6f
8 touches
6 conflicts
0xf0438fc4…e865
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
6 touches
3 conflicts
0x7bf008c3…917e
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity