← previous blocknext block →recent activity

Analyzing

Block #109,170,070

26 transactions · 21 stateful · 2026-09-29 23:43:22 UTC

Parallelism

62/100

Blocked

48%

Avg conflicts / tx

1.19

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #109,170,070  ·  26 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x7d9ef283…ddd1

0x34b655…2a6f

12 touches
15 conflicts

0xbd590df7…9891

0x34b655…2a6f

8 touches
6 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xf5dc501b…831c

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x15698ac9…2a46

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 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 0x7d9ef2836a…01ddd1

← previous block·next block →recent activity