← previous blocknext block →recent activity

Analyzing

Block #105,856,124

23 transactions · 22 stateful · 2026-09-18 09:31:53 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

1.26

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #105,856,124  ·  23 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

0x297de2d5…7396

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xcaa9e7c9…bc79

0x34b655…2a6f

12 touches
15 conflicts

0x38e0e818…ed23

0x34b655…2a6f

10 touches
10 conflicts

0xd6d040d9…9ae3

0x34b655…2a6f

8 touches
6 conflicts

0xd79c9727…1233

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x74a21ae3…38f9

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

21 conflicts on slot 0x297de2d577…2b7396

← previous block·next block →recent activity