← previous blocknext block →recent activity

Analyzing

Block #101,322,013

19 transactions · 18 stateful · 2026-09-02 11:56:37 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,322,013  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xbd590df7…9891

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

8 touches
6 conflicts

0xbb975a6c…bff4

0x34b655…2a6f

6 touches
3 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

6 touches
3 conflicts

0x9b334941…fddf

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

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

6 conflicts on slot 0xbd590df7f7…cf9891

← previous block·next block →recent activity