← previous blocknext block →recent activity
Analyzing
Block #99,450,117
24 transactions · 24 stateful · 2026-08-26 22:38:34 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.96
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,450,117 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w17w08w19w010w111w112w215w216w217w319w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bf239bd…46ad
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x70d81211…f49f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
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 0x1bf239bde7…4d46ad
Audit this contract →
← previous block·next block →recent activity