← previous blocknext block →recent activity

Analyzing

Block #102,526,998

19 transactions · 19 stateful · 2026-09-06 17:22:45 UTC

Parallelism

74/100

Blocked

32%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,526,998  ·  19 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

0x54fe7e99…7139

0x34b655…2a6f

8 touches
6 conflicts

0x6183ee9a…21b1

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x3e3f27ce…580c

0x34b655…2a6f

4 touches
1 conflict

0x42e5184f…4e8b

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5317

0x34b655…2a6f

4 touches
1 conflict

0x641aed07…bcb9

0x34b655…2a6f

4 touches
1 conflict

0x6636a104…d595

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

6 conflicts on slot 0x54fe7e9943…507139

← previous block·next block →recent activity