← previous blocknext block →recent activity
Analyzing
Block #99,205,733
11 transactions · 10 stateful · 2026-08-26 02:08:25 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,205,733 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcda60cc8…575b
0x34b655…2a6f
4 touches
1 conflict
0xd6113c0f…0a4b
0x34b655…2a6f
4 touches
1 conflict
0xfa09be5a…1e79
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x18a8536c…4a40
0x34b655…2a6f
4 touches
1 conflict
0x1d5fcf59…7fb9
0x34b655…2a6f
4 touches
1 conflict
0x2121b1b0…cc4e
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 0xcda60cc821…a0575b
Audit this contract →
← previous block·next block →recent activity