← previous blocknext block →recent activity

Analyzing

Block #101,150,065

18 transactions · 18 stateful · 2026-09-01 21:31:33 UTC

Parallelism

89/100

Blocked

22%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #101,150,065  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…642d

0x34b655…2a6f

4 touches
1 conflict

0xc9c17729…ac91

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x4d5053d1…3b7d

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

1 conflict on slot 0xf8f1e808d4…5ca4fd

← previous block·next block →recent activity