← previous blocknext block →recent activity

Analyzing

Block #102,063,935

16 transactions · 15 stateful · 2026-09-05 02:15:48 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.69

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,063,935  ·  16 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

0xd4893967…d7f3

0x34b655…2a6f

6 touches
3 conflicts

0x91b13e91…855d

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xba5743c7…21c3

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x3774a68c…11ff

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 0xd48939674c…46d7f3

← previous block·next block →recent activity