← previous blocknext block →recent activity

Analyzing

Block #99,080,672

30 transactions · 23 stateful · 2026-08-25 15:38:57 UTC

Parallelism

70/100

Blocked

61%

Avg conflicts / tx

1.13

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #99,080,672  ·  30 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xca841faa…486a

0x34b655…2a6f

14 touches
21 conflicts

0xa02838a3…bc54

0x34b655…2a6f

6 touches
3 conflicts

0xa05dafe7…aff6

0x34b655…2a6f

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xd5ad0af4…2387

0x34b655…2a6f

6 touches
3 conflicts

0xfaf5fe80…1ffc

0x34b655…2a6f

6 touches
3 conflicts

0x08db2444…22b2

0x34b655…2a6f

6 touches
3 conflicts

0x9f63b181…919d

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

21 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity