← previous blocknext block →recent activity
Analyzing
Block #99,205,029
21 transactions · 17 stateful · 2026-08-26 02:04:53 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,205,029 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w211w312w413w014w116w217w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x55010ec8…ea31
0x34b655…2a6f
10 touches
10 conflicts
0x9b0b6ae5…8cd9
0x34b655…2a6f
10 touches
10 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0x48203298…65cb
0x34b655…2a6f
6 touches
3 conflicts
0x8383cd6c…9e62
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity