← previous blocknext block →recent activity

Analyzing

Block #102,854,697

27 transactions · 24 stateful · 2026-09-07 20:58:22 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

1.07

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,854,697  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xa1087a5c…66c4

0x754704…b603

14 touches
21 conflicts

0x11b69a7e…334e

0x01bff4…1071

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0xd5218c2b…597d

0x851145…3f07

9 touches
10 conflicts

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0xb87af72a…aef6

0x2a68ba…90c5

4 touches
1 conflict

0x948836ff…59ab

0x34b655…2a6f

4 touches
1 conflict

0xd66696e0…0842

0x34b655…2a6f

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)

21 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity