← previous blocknext block →recent activity

Analyzing

Block #108,989,263

31 transactions · 23 stateful · 2026-09-29 08:31:19 UTC

Parallelism

68/100

Blocked

57%

Avg conflicts / tx

1.32

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #108,989,263  ·  31 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

0xca841faa…486a

0x34b655…2a6f

18 touches
36 conflicts

0x1c414c9c…ccc1

0x34b655…2a6f

8 touches
6 conflicts

0x3b99565b…6441

0x34b655…2a6f

8 touches
6 conflicts

0x3e1124f3…1035

0x34b655…2a6f

8 touches
6 conflicts

0x40d6d1e9…131e

0x34b655…2a6f

8 touches
6 conflicts

0x466771e2…9731

0x34b655…2a6f

8 touches
6 conflicts

0x5ad5e6de…e7ad

0x34b655…2a6f

8 touches
6 conflicts

0x7006165a…df17

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

36 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity