← previous blocknext block →recent activity

Analyzing

Block #101,798,935

16 transactions · 16 stateful · 2026-09-04 03:55:58 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,798,935  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x6d1b72ee…6b78

0x34b655…2a6f

6 touches
3 conflicts

0x15698ac9…2a46

0x34b655…2a6f

4 touches
1 conflict

0xd7668c61…55f8

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x521ca204…da49

0x34b655…2a6f

4 touches
1 conflict

0x366a19b0…f065

0x34b655…2a6f

2 touches
0 conflicts

0x386e26c3…fa30

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0x6d1b72eefe…416b78

← previous block·next block →recent activity