← previous blocknext block →recent activity

Analyzing

Block #100,917,303

19 transactions · 18 stateful · 2026-09-01 02:00:13 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,917,303  ·  19 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

0x27824ec7…7816

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x894e3d9d…46c1

0x34b655…2a6f

6 touches
3 conflicts

0x25180879…8191

0x34b655…2a6f

6 touches
3 conflicts

0x065d4a9d…9e00

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x53f7214d…8ec6

0x34b655…2a6f

4 touches
1 conflict

0x7d6b9af1…9a38

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

3 conflicts on slot 0x27824ec758…5b7816

← previous block·next block →recent activity