← previous blocknext block →recent activity

Analyzing

Block #100,628,293

30 transactions · 20 stateful · 2026-08-31 01:46:01 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,628,293  ·  30 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x5684aadd…8d62

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xa1382963…84c6

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x038b9243…553d

0x34b655…2a6f

4 touches
1 conflict

0x0a809ce1…7894

0x34b655…2a6f

4 touches
1 conflict

0x315e07b8…9823

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity