← previous blocknext block →recent activity

Analyzing

Block #101,797,657

24 transactions · 22 stateful · 2026-09-04 03:49:32 UTC

Parallelism

71/100

Blocked

59%

Avg conflicts / tx

1.46

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #101,797,657  ·  24 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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x4ee0b65a…6d40

0x34b655…2a6f

6 touches
3 conflicts

0x4089d428…b018

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x03f79551…7bc7

0x34b655…2a6f

4 touches
1 conflict

0x0a6f5e37…6c3c

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