← previous blocknext block →recent activity

Analyzing

Block #108,512,546

18 transactions · 17 stateful · 2026-09-27 16:26:28 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #108,512,546  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x60a536a6…ef7a

0x34b655…2a6f

6 touches
3 conflicts

0xb143ce0e…5897

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0xedf4c3b5…eff3

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0x3e04662b…0da6

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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 0x60a536a6ee…6aef7a

← previous block·next block →recent activity