← previous blocknext block →recent activity

Analyzing

Block #105,925,585

42 transactions · 38 stateful · 2026-09-18 15:22:22 UTC

Parallelism

67/100

Blocked

55%

Avg conflicts / tx

1.83

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #105,925,585  ·  42 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xd17580f9…ece1

0x754704…b603

10 touches
10 conflicts

0x4089d428…b018

0x34b655…2a6f

8 touches
6 conflicts

0x6dcc4bf3…eb84

0x34b655…2a6f

8 touches
6 conflicts

0x86cea35b…bdff

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity