← previous blocknext block →recent activity

Analyzing

Block #105,856,389

22 transactions · 21 stateful · 2026-09-18 09:33:13 UTC

Parallelism

64/100

Blocked

52%

Avg conflicts / tx

1.45

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #105,856,389  ·  22 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

0xb194d30c…6af3

0x34b655…2a6f

14 touches
21 conflicts

0x97e4c862…4419

0x34b655…2a6f

12 touches
15 conflicts

0xd911522b…e960

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x4abfb389…18f4

0x34b655…2a6f

6 touches
3 conflicts

0xd6d040d9…9ae3

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x74a21ae3…38f9

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

21 conflicts on slot 0xb194d30c47…4d6af3

← previous block·next block →recent activity