← previous blocknext block →recent activity

Analyzing

Block #102,253,394

24 transactions · 24 stateful · 2026-09-05 18:16:11 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,253,394  ·  24 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

0x5150abbe…43c3

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0xfd2dda58…d62a

0x34b655…2a6f

6 touches
3 conflicts

0xac4971f2…200b

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x786d66ce…ae70

0x34b655…2a6f

4 touches
1 conflict

0xfaf89f45…ced6

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)

15 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity