← previous blocknext block →recent activity

Analyzing

Block #103,040,852

13 transactions · 13 stateful · 2026-09-08 12:35:43 UTC

Parallelism

85/100

Blocked

23%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #103,040,852  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x1470cae0…177e

0x34b655…2a6f

4 touches
1 conflict

0x483c2974…bee4

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x6c28863e…840e

0x34b655…2a6f

4 touches
1 conflict

0x7b67f6cf…0aab

0x34b655…2a6f

4 touches
1 conflict

0xadc848ee…5cb2

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)

1 conflict on slot 0xd17580f913…78ece1

← previous block·next block →recent activity