← previous blocknext block →recent activity

Analyzing

Block #108,619,136

25 transactions · 22 stateful · 2026-09-28 01:23:14 UTC

Parallelism

56/100

Blocked

59%

Avg conflicts / tx

1.32

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #108,619,136  ·  25 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x8c35871e…8931

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1d6cb721…c88c

0x34b655…2a6f

6 touches
3 conflicts

0x9375a764…dca1

0x34b655…2a6f

4 touches
1 conflict

0x9cf9bac2…dee7

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity