← previous blocknext block →recent activity

Analyzing

Block #106,473,830

21 transactions · 19 stateful · 2026-09-20 13:21:48 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,473,830  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xfd4e632c…e14c

0x34b655…2a6f

12 touches
15 conflicts

0x22659874…ec0b

0x34b655…2a6f

10 touches
10 conflicts

0x739123da…57f3

0x34b655…2a6f

8 touches
6 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

8 touches
6 conflicts

0x5b7fec07…7153

0x34b655…2a6f

6 touches
3 conflicts

0xb7e8b0c4…dec3

0x34b655…2a6f

6 touches
3 conflicts

0xbd3735d7…c973

0x34b655…2a6f

6 touches
3 conflicts

0xc04a9203…7d63

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

15 conflicts on slot 0xfd4e632c76…e1e14c

← previous block·next block →recent activity