← previous blocknext block →recent activity

Analyzing

Block #105,921,084

20 transactions · 19 stateful · 2026-09-18 14:59:42 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.8

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #105,921,084  ·  20 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

0xd17580f9…ece1

0x754704…b603

10 touches
10 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x5070f68d…d86f

0x34b655…2a6f

6 touches
3 conflicts

0xce2afb0d…94be

0x34b655…2a6f

6 touches
3 conflicts

0x206f4379…e08a

0x34b655…2a6f

6 touches
3 conflicts

0x20b1228b…2487

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 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)

10 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity