← previous blocknext block →recent activity

Analyzing

Block #102,205,386

22 transactions · 21 stateful · 2026-09-05 14:13:03 UTC

Parallelism

73/100

Blocked

43%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,205,386  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0x483c2974…bee4

0x34b655…2a6f

6 touches
3 conflicts

0x247cfb80…cca8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x045532dd…4b7d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002f

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

6 conflicts on slot 0x51fc8795c8…57126f

← previous block·next block →recent activity