← previous blocknext block →recent activity

Analyzing

Block #101,673,849

27 transactions · 24 stateful · 2026-09-03 17:26:50 UTC

Parallelism

63/100

Blocked

42%

Avg conflicts / tx

0.85

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #101,673,849  ·  27 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x0b3a121c…f803

0x34b655…2a6f

4 touches
1 conflict

0x33c321d6…b941

0x34b655…2a6f

4 touches
1 conflict

0xdbb571e4…6829

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity