← previous blocknext block →recent activity

Analyzing

Block #106,551,164

18 transactions · 18 stateful · 2026-09-20 19:51:00 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #106,551,164  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x08943ea2…ed03

0x754704…b603

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 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: USDC (USDC)

3 conflicts on slot 0x08943ea26c…67ed03

← previous block·next block →recent activity