← previous blocknext block →recent activity

Analyzing

Block #99,099,010

17 transactions · 16 stateful · 2026-08-25 17:11:24 UTC

Parallelism

82/100

Blocked

19%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,099,010  ·  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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf06fce24…887d

0x34b655…2a6f

4 touches
1 conflict

0xf27d6ce8…cf9f

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x5ce19b50…f20f

0x34b655…2a6f

4 touches
1 conflict

0x64275949…d698

0x34b655…2a6f

4 touches
1 conflict

0x74f93c44…7cd9

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity