← previous blocknext block →recent activity
Analyzing
Block #99,255,965
21 transactions · 18 stateful · 2026-08-26 06:21:10 UTC
Parallelism
67/100
Blocked
67%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,255,965 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w29w010w312w213w314w418w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3f2100d8…f9b5
0xa6afd3…d132
6 touches
3 conflicts
0x497d19bc…865e
0x34b655…2a6f
6 touches
3 conflicts
0xa366dc41…b2d8
0xa6afd3…d132
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity