← previous blocknext block →recent activity

Analyzing

Block #106,272,173

18 transactions · 17 stateful · 2026-09-19 20:26:54 UTC

Parallelism

61/100

Blocked

47%

Avg conflicts / tx

1.28

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,272,173  ·  18 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

0xd17580f9…ece1

0x754704…b603

14 touches
21 conflicts

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x1dfc34bb…34e9

0x34b655…2a6f

4 touches
1 conflict

0x061ff587…7595

0x34b655…2a6f

2 touches
0 conflicts

0x0fc536fb…1aa1

0x34b655…2a6f

2 touches
0 conflicts

0x1c255088…e409

0x34b655…2a6f

2 touches
0 conflicts

0x310a7246…2dcb

0x34b655…2a6f

2 touches
0 conflicts

0x513afe22…68cf

0x34b655…2a6f

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)

21 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity