← previous blocknext block →recent activity
Analyzing
Block #99,211,261
17 transactions · 16 stateful · 2026-08-26 02:36:13 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,211,261 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w18w19w011w012w113w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ee33109…7176
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb520677b…19f0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x6098b25a…79dd
0x34b655…2a6f
4 touches
1 conflict
0x192a1fc3…9766
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
1 conflict on slot 0x4ee33109d2…6b7176
Audit this contract →
← previous block·next block →recent activity