← previous blocknext block →recent activity

Analyzing

Block #100,984,046

21 transactions · 18 stateful · 2026-09-01 07:35:57 UTC

Parallelism

52/100

Blocked

50%

Avg conflicts / tx

1.24

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #100,984,046  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xd2fd6de4…1729

0x34b655…2a6f

12 touches
15 conflicts

0x9a100e05…c541

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x35006f8a…8e7f

0x34b655…2a6f

8 touches
6 conflicts

0x953517cb…cdec

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x4a538b72…479c

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

15 conflicts on slot 0xd2fd6de4a1…5c1729

← previous block·next block →recent activity