← previous blocknext block →recent activity

Analyzing

Block #106,420,466

21 transactions · 19 stateful · 2026-09-20 08:53:10 UTC

Parallelism

67/100

Blocked

42%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,420,466  ·  21 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

0xa8a44b97…b097

0x34b655…2a6f

12 touches
15 conflicts

0x2130a548…c1de

0x34b655…2a6f

8 touches
6 conflicts

0xbe9d1d23…3de2

0x34b655…2a6f

8 touches
6 conflicts

0x5655f5c3…6b75

0x34b655…2a6f

6 touches
3 conflicts

0x810a3aa2…0227

0x34b655…2a6f

6 touches
3 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xfd4e632c…e14c

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

15 conflicts on slot 0xa8a44b9722…deb097

← previous block·next block →recent activity