← previous blocknext block →recent activity
Analyzing
Block #99,209,405
13 transactions · 13 stateful · 2026-08-26 02:26:53 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,209,405 · 13 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
1w04w06w18w110w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x191eae88…6e80
0x34b655…2a6f
4 touches
1 conflict
0xb54c8ced…5b8c
0x34b655…2a6f
4 touches
1 conflict
0xbaf6ed88…c179
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd9c05bd7…8cc8
0x34b655…2a6f
3 touches
1 conflict
0x55753ef0…42fa
0xd32edf…ff58
3 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
2 touches
0 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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity