← previous blocknext block →recent activity

Analyzing

Block #100,461,925

23 transactions · 23 stateful · 2026-08-30 11:49:05 UTC

Parallelism

74/100

Blocked

35%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,461,925  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

2 touches
0 conflicts

0x260cc5c4…bef0

0x2b46c0…1669

2 touches
0 conflicts

0x39977254…07b1

0x2b46c0…1669

2 touches
0 conflicts

0x62811193…1869

0x2b46c0…1669

2 touches
0 conflicts

0x62811193…186c

0x2b46c0…1669

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)

15 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity