← previous blocknext block →recent activity

Analyzing

Block #106,930,943

18 transactions · 18 stateful · 2026-09-22 03:43:29 UTC

Parallelism

61/100

Blocked

56%

Avg conflicts / tx

1.72

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,930,943  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x574628e9…dcc3

0x34b655…2a6f

14 touches
21 conflicts

0x42522e76…2592

0x34b655…2a6f

10 touches
10 conflicts

0x16eed475…62dc

0x34b655…2a6f

10 touches
10 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

10 touches
10 conflicts

0xf8d9af5e…eba6

0x34b655…2a6f

10 touches
10 conflicts

0xd4230a60…bd13

0x34b655…2a6f

10 touches
10 conflicts

0x721c4bf6…290c

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

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 0x574628e919…e4dcc3

← previous block·next block →recent activity