← previous blocknext block →recent activity
Analyzing
Block #99,352,532
25 transactions · 23 stateful · 2026-08-26 14:27:02 UTC
Parallelism
80/100
Blocked
65%
Avg conflicts / tx
1.16
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,352,532 · 25 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
2w03w05w16w28w19w210w312w113w214w315w417w318w119w220w221w324w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70e677f5…e3bd
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xfa0c5188…06f2
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x916ffa0b…56ad
0x34b655…2a6f
6 touches
3 conflicts
0x4038f924…39a1
0x34b655…2a6f
6 touches
3 conflicts
0x8640741b…8b82
0x34b655…2a6f
6 touches
3 conflicts
0xff5aca62…b59b
0xd32edf…ff58
5 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
6 conflicts on slot 0x70e677f5c0…90e3bd
Audit this contract →
← previous block·next block →recent activity