← previous blocknext block →recent activity

Analyzing

Block #102,475,890

18 transactions · 17 stateful · 2026-09-06 13:03:25 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,475,890  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0xa605468c…1bfc

0x34ae4d…3fc5

2 touches
0 conflicts

0x00000000…003d

0x40c49f…2af0

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

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)

6 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity