← previous blocknext block →recent activity

Analyzing

Block #100,584,645

20 transactions · 17 stateful · 2026-08-30 22:06:26 UTC

Parallelism

75/100

Blocked

41%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,584,645  ·  20 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xb4c703ab…f8cf

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0xe38669b7…bbe5

0x34b655…2a6f

6 touches
3 conflicts

0x00c8447e…a888

0x34b655…2a6f

4 touches
1 conflict

0x258fcaf5…2084

0x34b655…2a6f

4 touches
1 conflict

0x41689b03…0dbc

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0xac2a02739b…81721b

← previous block·next block →recent activity