← previous blocknext block →recent activity

Analyzing

Block #101,670,188

21 transactions · 19 stateful · 2026-09-03 17:08:25 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.9

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,670,188  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x56e0d685…c960

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0xa1a01ded…c087

0x34b655…2a6f

6 touches
3 conflicts

0xbb9ab337…f4ec

0x34b655…2a6f

6 touches
3 conflicts

0xddf10453…d774

0x34b655…2a6f

6 touches
3 conflicts

0xeb1b66a1…ce4e

0x34b655…2a6f

6 touches
3 conflicts

0xeb4304a5…dd06

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity