← previous blocknext block →recent activity

Analyzing

Block #105,377,697

32 transactions · 28 stateful · 2026-09-16 17:22:25 UTC

Parallelism

84/100

Blocked

25%

Avg conflicts / tx

0.41

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #105,377,697  ·  32 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

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x919d5105…a3b0

0x065c9d…c394

2 touches
0 conflicts

0xf93786ac…f4cb

0x065c9d…c394

2 touches
0 conflicts

0xfcb3615b…5501

0x065c9d…c394

2 touches
0 conflicts

0xb87af72a…aef6

0x2a68ba…90c5

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)

10 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity