← previous blocknext block →recent activity

Analyzing

Block #105,852,924

30 transactions · 28 stateful · 2026-09-18 09:15:47 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

1.73

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #105,852,924  ·  30 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x831f75b4…945d

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x206f4379…e08a

0x34b655…2a6f

8 touches
6 conflicts

0x30eb4826…3990

0x34b655…2a6f

8 touches
6 conflicts

0x281eb718…6779

0x34b655…2a6f

8 touches
6 conflicts

0x9e4f30ea…3d07

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

28 conflicts on slot 0x831f75b4aa…17945d

← previous block·next block →recent activity