← previous blocknext block →recent activity

Analyzing

Block #102,861,448

25 transactions · 22 stateful · 2026-09-07 21:32:19 UTC

Parallelism

64/100

Blocked

68%

Avg conflicts / tx

2.04

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #102,861,448  ·  25 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

16 touches
28 conflicts

0xaad6be10…0801

0x2a68ba…90c5

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0x11b69a7e…334e

0x01bff4…1071

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0xa20e4268…fbee

0x851145…3f07

9 touches
10 conflicts

0xb686e6f5…f6d1

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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)

28 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity