← previous blocknext block →recent activity

Analyzing

Block #105,870,403

16 transactions · 16 stateful · 2026-09-18 10:43:45 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

1.13

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #105,870,403  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

8 touches
6 conflicts

0xfe0a0e55…2f0a

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0xbd590df7…9891

0x34b655…2a6f

6 touches
3 conflicts

0xbc8fb280…76a3

0x34b655…2a6f

6 touches
3 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

6 touches
3 conflicts

0x5ad5e6de…e7ad

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity