← previous blocknext block →recent activity

Analyzing

Block #102,189,496

20 transactions · 19 stateful · 2026-09-05 12:52:28 UTC

Parallelism

85/100

Blocked

26%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,189,496  ·  20 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

0x56a284d9…32e4

0x34b655…2a6f

6 touches
3 conflicts

0x810bee1d…0817

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x588380ee…0a5c

0x34b655…2a6f

4 touches
1 conflict

0x73d35a6e…6abb

0x34b655…2a6f

4 touches
1 conflict

0x7d6b9af1…9a38

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

3 conflicts on slot 0x56a284d9bf…3432e4

← previous block·next block →recent activity