← previous blocknext block →recent activity

Analyzing

Block #105,848,891

26 transactions · 20 stateful · 2026-09-18 08:55:29 UTC

Parallelism

69/100

Blocked

40%

Avg conflicts / tx

1.12

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #105,848,891  ·  26 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xf233f777…0411

0x34b655…2a6f

12 touches
15 conflicts

0x97e4c862…4419

0x34b655…2a6f

10 touches
10 conflicts

0xc09c3422…3c8b

0x34b655…2a6f

10 touches
10 conflicts

0x4118bd12…924a

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x297de2d5…7396

0x34b655…2a6f

6 touches
3 conflicts

0x161d8cf7…654b

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 0xc824469a90…af6425

← previous block·next block →recent activity