← previous blocknext block →recent activity

Analyzing

Block #102,745,207

19 transactions · 18 stateful · 2026-09-07 11:44:16 UTC

Parallelism

84/100

Blocked

39%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,745,207  ·  19 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

0xfddbcd2e…b20f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xfaf5fe80…1ffc

0x34b655…2a6f

6 touches
3 conflicts

0x300f56a7…4a30

0xd32edf…ff58

5 touches
3 conflicts

0x3b6e959d…158f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x1f8a126c…9aa2

0x1b6862…e19c

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 0xfddbcd2e68…c4b20f

← previous block·next block →recent activity