← previous blocknext block →recent activity

Analyzing

Block #106,367,475

22 transactions · 21 stateful · 2026-09-20 04:26:29 UTC

Parallelism

45/100

Blocked

67%

Avg conflicts / tx

3.09

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #106,367,475  ·  22 txs across 12 waves  ·  depth 12
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

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

0xb1abac7e…cb5b

0x34b655…2a6f

22 touches
55 conflicts

0x99031764…b5e6

0x34b655…2a6f

12 touches
15 conflicts

0x89eaf36a…4e48

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xe283e878…7262

0x34b655…2a6f

10 touches
10 conflicts

0x8d175439…fb79

0x34b655…2a6f

8 touches
6 conflicts

0x2130a548…c1de

0x34b655…2a6f

8 touches
6 conflicts

0x0463db49…5d05

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

55 conflicts on slot 0xb1abac7e42…85cb5b

← previous block·next block →recent activity