← previous blocknext block →recent activity

Analyzing

Block #105,850,027

24 transactions · 24 stateful · 2026-09-18 09:01:12 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #105,850,027  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

0xacbe13f3…10f0

0x34b655…2a6f

4 touches
1 conflict

0xb9a687de…b8a1

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea67acfe…2037

0x34b655…2a6f

4 touches
1 conflict

0xf397d89f…f80e

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)

6 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity