← previous blocknext block →recent activity

Analyzing

Block #99,205,379

16 transactions · 15 stateful · 2026-08-26 02:06:38 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,205,379  ·  16 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x2202504e…fad0

0x34b655…2a6f

10 touches
10 conflicts

0xd4b8e8da…2e35

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

4 touches
1 conflict

0x55010ec8…ea31

0x34b655…2a6f

4 touches
1 conflict

0x72083f0d…082a

0x34b655…2a6f

4 touches
1 conflict

0x98854ef0…1f3c

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

10 conflicts on slot 0x2202504ef1…9ffad0

← previous block·next block →recent activity