← previous blocknext block →recent activity

Analyzing

Block #102,567,028

25 transactions · 23 stateful · 2026-09-06 20:45:41 UTC

Parallelism

80/100

Blocked

30%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,567,028  ·  25 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

0x2c9fd1d7…40c4

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x53c41998…7d52

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x290abc80…f606

0x34b655…2a6f

4 touches
1 conflict

0x5150abbe…43c3

0x34b655…2a6f

4 touches
1 conflict

0x939cdd56…00c8

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 0x2c9fd1d77c…1840c4

← previous block·next block →recent activity