← previous blocknext block →recent activity

Analyzing

Block #106,468,623

23 transactions · 20 stateful · 2026-09-20 12:55:35 UTC

Parallelism

78/100

Blocked

35%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,468,623  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe99e28c5…e95d

0x34b655…2a6f

8 touches
6 conflicts

0x46c14e01…ff09

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0x0463db49…5d05

0x34b655…2a6f

4 touches
1 conflict

0x1b25f260…c429

0x34b655…2a6f

4 touches
1 conflict

0x9ff4ca89…6115

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 0xe99e28c54c…90e95d

← previous block·next block →recent activity