← previous blocknext block →recent activity

Analyzing

Block #100,736,699

22 transactions · 20 stateful · 2026-08-31 10:51:20 UTC

Parallelism

50/100

Blocked

65%

Avg conflicts / tx

2.32

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #100,736,699  ·  22 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xac2a0273…721b

0x34b655…2a6f

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x737acb78…fce8

0x34b655…2a6f

16 touches
28 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

12 touches
15 conflicts

0xec7d120d…7084

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x1d6ce97a…901b

0x34b655…2a6f

6 touches
3 conflicts

0xfa159960…9edb

0x34b655…2a6f

6 touches
3 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

28 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity