← previous blocknext block →recent activity

Analyzing

Block #106,363,248

21 transactions · 21 stateful · 2026-09-20 04:05:13 UTC

Parallelism

57/100

Blocked

57%

Avg conflicts / tx

1.95

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #106,363,248  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xba33378a…f1df

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x7d8688d3…d0a3

0x34b655…2a6f

8 touches
6 conflicts

0xda43ef99…b093

0x34b655…2a6f

8 touches
6 conflicts

0x6771eae2…7014

0x34b655…2a6f

6 touches
3 conflicts

0x1b25f260…c429

0x34b655…2a6f

6 touches
3 conflicts

0x2130a548…c1de

0x34b655…2a6f

6 touches
3 conflicts

0x49b9fdd5…9c16

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 0xba33378abc…73f1df

← previous block·next block →recent activity