← previous blocknext block →recent activity

Analyzing

Block #106,801,423

19 transactions · 18 stateful · 2026-09-21 16:51:33 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

0.84

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,801,423  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x0fb20484…1982

0x34b655…2a6f

4 touches
1 conflict

0x1dc6858a…0ea8

0x34b655…2a6f

4 touches
1 conflict

0x2249932e…474a

0x34b655…2a6f

4 touches
1 conflict

0x29a58269…011a

0x34b655…2a6f

4 touches
1 conflict

0x2a3f40b6…e39c

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity