← previous blocknext block →recent activity

Analyzing

Block #104,977,077

21 transactions · 21 stateful · 2026-09-15 07:46:05 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #104,977,077  ·  21 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

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x10f0a1bf…12c3

0x34b655…2a6f

2 touches
0 conflicts

0x3347cbe5…846c

0x34b655…2a6f

2 touches
0 conflicts

0x33da0dfa…bac6

0x34b655…2a6f

2 touches
0 conflicts

0x59dccbd8…2bf6

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