← previous blocknext block →recent activity

Analyzing

Block #108,605,431

26 transactions · 21 stateful · 2026-09-28 00:14:12 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.69

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #108,605,431  ·  26 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x0d54fa3e…3b3c

0x34b655…2a6f

8 touches
6 conflicts

0x0ddc998e…def8

0x34b655…2a6f

8 touches
6 conflicts

0x16d77246…bac5

0x34b655…2a6f

8 touches
6 conflicts

0x280aaa58…1c52

0x34b655…2a6f

8 touches
6 conflicts

0x309f47c0…e1cf

0x34b655…2a6f

8 touches
6 conflicts

0x3b65c5ca…9f83

0x34b655…2a6f

8 touches
6 conflicts

0x4c71d355…5ace

0x34b655…2a6f

8 touches
6 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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity