← previous blocknext block →recent activity

Analyzing

Block #108,965,070

38 transactions · 27 stateful · 2026-09-29 06:29:03 UTC

Parallelism

71/100

Blocked

48%

Avg conflicts / tx

1.13

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #108,965,070  ·  38 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

0x631b4113…baa9

0x34b655…2a6f

16 touches
28 conflicts

0x342fe47d…42ae

0x34b655…2a6f

12 touches
15 conflicts

0x3a3c1ed9…9dd5

0x34b655…2a6f

12 touches
15 conflicts

0x48719cbe…5484

0x34b655…2a6f

12 touches
15 conflicts

0x69a58eaa…38a1

0x34b655…2a6f

12 touches
15 conflicts

0x6b583dde…23c7

0x34b655…2a6f

12 touches
15 conflicts

0x751f0341…fe9b

0x34b655…2a6f

12 touches
15 conflicts

0x013496f9…fb8e

0x34b655…2a6f

12 touches
15 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

28 conflicts on slot 0x631b41138f…31baa9

← previous block·next block →recent activity