← previous blocknext block →recent activity

Analyzing

Block #101,091,930

28 transactions · 24 stateful · 2026-09-01 16:39:06 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.96

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #101,091,930  ·  28 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xca841faa…486a

0x34b655…2a6f

14 touches
21 conflicts

0x729c91b8…9538

0x188d58…ea8e

4 touches
1 conflict

0x00f19757…9252

0x34b655…2a6f

4 touches
1 conflict

0x0423aaa6…5aaa

0x34b655…2a6f

4 touches
1 conflict

0x0476d77b…a514

0x34b655…2a6f

4 touches
1 conflict

0x077d58c3…8ed7

0x34b655…2a6f

4 touches
1 conflict

0x23253ea8…e0a4

0x34b655…2a6f

4 touches
1 conflict

0x2a949bb2…8769

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

21 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity