← previous blocknext block →recent activity
Analyzing
Block #99,448,193
22 transactions · 17 stateful · 2026-08-26 22:28:52 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,448,193 · 22 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
2w05w07w18w29w010w111w312w313w417w518w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6324ccc9…14fd
0x34b655…2a6f
8 touches
6 conflicts
0xc875a359…49fb
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3a7fb5b5…f0e5
0x34b655…2a6f
6 touches
3 conflicts
0x7b8690aa…2582
0x34b655…2a6f
6 touches
3 conflicts
0x17a7f697…dcb8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2d9e167d…d3f8
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 0x6324ccc962…7f14fd
Audit this contract →
← previous block·next block →recent activity