← previous blocknext block →recent activity

Analyzing

Block #102,230,039

22 transactions · 22 stateful · 2026-09-05 16:17:46 UTC

Parallelism

68/100

Blocked

36%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,230,039  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x00532bf5…5711

0x754704…b603

4 touches
1 conflict

0x0eff0903…8165

0x754704…b603

4 touches
1 conflict

0x51fc8795…1266

0x34b655…2a6f

4 touches
1 conflict

0xe9e92bac…00ed

0x754704…b603

4 touches
1 conflict

0x68c08dd2…be14

0x99c7a7…8bf0

4 touches
1 conflict

0xdfac3ce0…6699

0x99c7a7…8bf0

4 touches
1 conflict

0x65f011a5…bc6e

0x34b655…2a6f

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)

21 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity