← previous blocknext block →recent activity

Analyzing

Block #108,619,759

25 transactions · 21 stateful · 2026-09-28 01:26:22 UTC

Parallelism

88/100

Blocked

24%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #108,619,759  ·  25 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

0x0fd61128…b00b

0x754704…b603

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x125f12…a50b

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4e44fd40…7335

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

1 conflict on slot 0x0fd611287d…30b00b

← previous block·next block →recent activity