← previous blocknext block →recent activity

Analyzing

Block #101,935,618

23 transactions · 21 stateful · 2026-09-04 15:25:22 UTC

Parallelism

74/100

Blocked

33%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,935,618  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x1dc71894…1884

0x34b655…2a6f

6 touches
3 conflicts

0xa1a01ded…c087

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xc853be2d…b18f

0x34b655…2a6f

6 touches
3 conflicts

0x67c1f465…38b3

0x34b655…2a6f

6 touches
3 conflicts

0x897879a1…9c78

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity