← previous blocknext block →recent activity

Analyzing

Block #100,438,264

22 transactions · 21 stateful · 2026-08-30 09:49:58 UTC

Parallelism

59/100

Blocked

43%

Avg conflicts / tx

1.73

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #100,438,264  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xad601853…1d2a

0x34b655…2a6f

4 touches
1 conflict

0x12e77486…ec2b

0x34b655…2a6f

2 touches
0 conflicts

0x3c9b10c1…d791

0x34b655…2a6f

2 touches
0 conflicts

0x6d5d1fb5…86a7

0x34b655…2a6f

2 touches
0 conflicts

0x90f65937…f295

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)

36 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity