← previous blocknext block →recent activity

Analyzing

Block #108,630,470

21 transactions · 21 stateful · 2026-09-28 02:20:18 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #108,630,470  ·  21 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

0x32674e3a…cd5c

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xfe46eb50…c3a9

0xd32edf…ff58

5 touches
3 conflicts

0x25957369…c648

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x038b9243…553d

0x34b655…2a6f

4 touches
1 conflict

0xb6fcbbb7…2b31

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

2 touches
0 conflicts

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 0x32674e3ae6…ddcd5c

← previous block·next block →recent activity